MCP server · Projects and team work
Atlassian Rovo MCP server
Connects an assistant to Jira, Confluence, Bitbucket Cloud, Compass and Loom on your Atlassian Cloud site via Atlassian’s hosted server.
- Maintainer
- Atlassian (official)
- Licence
- Apache-2.0
- Runs
- Remote (URL)
- Sign-in
- OAuth sign-in in the app
- Registry version
- 2.0.0 (updated 2026-09-09)
- Last activity
- 2026-10-10
Overview
What it does
Atlassian’s MCP server is a cloud-hosted bridge between your Atlassian Cloud site and AI tools. It covers Jira, Confluence, Jira Service Management, Bitbucket Cloud, Compass, Loom and platform data such as Goals, Projects and Teams. Clients connect to https://mcp.atlassian.com/v2/mcp and sign in with OAuth 2.1, or use an API token for headless setups. Desktop clients without remote support use the mcp-remote proxy. The GitHub repository holds documentation and plugin packaging rather than server code.
Pick it when your team tracks work in Jira and writes in Confluence and you want an assistant to search issues, draft pages or link work across products. The server shows a small set of primary tools and lets the client discover the rest on demand, which saves context; gateways can add ?tools=all to get a flat list instead. Tools sit in permission groups such as read_jira, write_jira and search_confluence, which organisation admins can grant or revoke. Jira Service Management tools work only with API token authentication.
Tools
What the assistant can do
- Search, read and update Jira issues
- Search, read and write Confluence pages
- Read and write Bitbucket Cloud data for linked workspaces
- Jira Service Management tools (API token only)
- Compass, Loom, Goals, Projects and Teams data
- Teamwork Graph search, including linked pull requests, builds and deployments
Install
Install Atlassian Rovo MCP server in your app
You need:
- An Atlassian Cloud site with Jira, Confluence, Jira Service Management, Bitbucket or Compass
- An MCP client with remote server support, or Node.js 18 or newer to run mcp-remote
- A browser for the OAuth flow, or an API token that an admin has enabled
Run in your project. --scope local keeps the servers private to you in this project; use user for every project.
claude mcp add --scope local --transport http atlassian https://mcp.atlassian.com/v2/mcp
- atlassian: sign in when the app asks (run /mcp in Claude Code).
Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.
{
"mcpServers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
- atlassian: sign in when the app asks (run /mcp in Claude Code).
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.
{
"mcpServers": {}
}
- atlassian is a remote server: add it as a custom connector (Customize → Connectors → + Add → Add custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors), with the URL https://mcp.atlassian.com/v2/mcp.
In your project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"atlassian": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
- atlassian: sign in when the app asks.
In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.
{
"servers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
- atlassian: sign in when the app asks.
macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.
{
"mcpServers": {
"atlassian": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
- atlassian: sign in when the app asks.
Want it alongside other servers? Open Atlassian Rovo MCP Server in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.
Before you install
- Actions run with your Atlassian permissions, so the assistant can change anything you can edit. The delete_jira and manage_jira groups are off by default and need an admin to turn them on.
- API token use must be enabled by an organisation admin. Create a scoped personal token (Basic auth) or a service account key (Bearer) with only the scopes you need.
- Organisation IP allowlists also apply to tool calls made through the server.
- A remote server sees whatever the assistant sends it. Sign in with the narrowest access the service offers. See how to choose a safe server.
Why it’s listed
Why we list it
The official route into Jira and Confluence for assistants, with admin-controlled permission groups and support for both OAuth and scoped tokens.
Related
More MCP servers
- Linear MCP serverLets an assistant find, create and update Linear issues, projects and comments through Linear’s hosted server.
- Notion MCPLets an assistant search, read, create and update pages and databases in your Notion workspace through Notion’s hosted server.
- Slack MCP serverLets an assistant search Slack, read channels and threads, send messages and work with canvases, files and lists.
- Asana MCP serverLets an assistant search, read, create and update Asana tasks, projects and portfolios through Asana’s hosted V2 server.
- Zapier MCPLets an assistant act in thousands of apps through your Zapier account, such as sending email, posting to Slack or updating a CRM.
All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?