Rovo Dev and Model Context Protocol (MCP)
What is Model Context Protocol (MCP)?
MCP is a standardized framework that lets AI large language models connect to external data, tools, and services.
By using MCP to connect Rovo Dev to other data sources, developers can enhance the quality of their AI-generated code by providing the model with rich, relevant context from outside your Atlassian site.
How does Rovo Dev use Model Context Protocol?
Rovo Dev CLI processes data on the user’s local device, and enables connections to third-party data sources via model context protocol (MCP).
Rovo Dev CLI automatically connects to the Atlassian MCP server, and users can choose to connect to other, third-party data sources by MCP as well.
When connected to a third-party data source, in some cases users may create prompts to send data outside of your Atlassian site. Before any data is transferred, users will receive a prompt to review the third-party tool being used to send data, and approve or decline it. Users should carefully review each request to make sure they trust the third-party tool, and that using it complies with any policies your organization has in place. No data will be transferred to third-party sources without explicit user approval. Data sent outside your site will not be subject to Atlassian terms.
When you connect to a third-party data source, you are responsible for following any terms and policies about the use of data from third-party products.
We prioritize security and control with Rovo Dev CLI by allowing users to connect only to third-party sources they trust and by providing administrators with the capability to turn RovoDev CLI off.
Was this helpful?