# How to connect the Atlassian Rovo MCP server To connect the official Atlassian Rovo MCP server, add https://mcp.atlassian.com/v2/mcp to your MCP client as a Streamable HTTP server, then sign in with OAuth when your client prompts you. For headless use, authenticate with an API token if your admin allows it. Atlassian Rovo documents setup for VS Code, Cursor, Claude Code, Claude, Codex, Windsurf and ChatGPT. - Endpoint: https://mcp.atlassian.com/v2/mcp - Transport: Streamable HTTP - Registry: com.atlassian/atlassian-mcp-server 2.0.0 - Publisher documentation reviewed: 2026-11-05 (not a tested connection) - Guide page: https://apitracker.io/mcp-guides/atlassian-mcp ## Before you start - An Atlassian Cloud site with at least one of Jira, Confluence, Jira Service Management, Bitbucket or Compass. Actions run with your existing permissions on that site. - Using the server consumes Rovo credits. Usage limits depend on your Atlassian plan. - If your organization uses IP allowlisting, requests must come from allowed IP addresses. Hosted AI clients send requests from the provider's own IP addresses, so being on an allowed VPN may not be enough. - An organization admin controls which tool groups are available, must enable delete and manage tools for Jira, and must turn on API token authentication before anyone can use it. ## Steps 1. **Open Atlassian's Rovo MCP server setup instructions for your client** 2. **Add the Atlassian Rovo MCP server to your client** Add https://mcp.atlassian.com/v2/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Atlassian also publishes plugins or extensions for Claude Desktop, Codex Desktop, Cursor and VS Code. Gateways that need every tool up front can add ?tools=all to the URL. The legacy /v1/sse endpoint is deprecated. 3. **Sign in to Atlassian and approve access in the browser window** 4. **For headless use, authenticate with an API token if your admin allows it** Send a personal API token as Basic authentication in the Authorization header, using your Atlassian account email and the token. For service accounts, send the service account API key as a bearer token in the Authorization header. Tokens aren't bound to one site, so clients must pass the cloud ID explicitly, and some tools aren't available with tokens. Jira Service Management supports only API token authentication, and Compass supports only OAuth. 5. **If you already use a v1 endpoint, expect v2 tools** On March 1, 2027 existing v1 connections start exposing v2 tools automatically. If a client fails to authenticate after the change, clear its cached client ID or .well-known credentials and connect again. 6. **List the server's tools** ## Questions ### What is the Atlassian Rovo MCP server URL? The official Atlassian Rovo MCP server is at https://mcp.atlassian.com/v2/mcp and uses the Streamable HTTP transport. ### How do I authenticate with the Atlassian Rovo MCP server? Sign in with OAuth when your client prompts you. For headless use, authenticate with an API token if your admin allows it: Send a personal API token as Basic authentication in the Authorization header, using your Atlassian account email and the token. For service accounts, send the service account API key as a bearer token in the Authorization header. Tokens aren't bound to one site, so clients must pass the cloud ID explicitly, and some tools aren't available with tokens. Jira Service Management supports only API token authentication, and Compass supports only OAuth. ### Which AI clients can use the Atlassian Rovo MCP server? Atlassian Rovo's documentation covers VS Code, Cursor, Claude Code, Claude, Codex, Windsurf and ChatGPT. Other clients that support remote Streamable HTTP MCP servers may also work. ### What do I need before connecting Atlassian Rovo MCP? An Atlassian Cloud site with at least one of Jira, Confluence, Jira Service Management, Bitbucket or Compass. Actions run with your existing permissions on that site. Using the server consumes Rovo credits. Usage limits depend on your Atlassian plan. If your organization uses IP allowlisting, requests must come from allowed IP addresses. Hosted AI clients send requests from the provider's own IP addresses, so being on an allowed VPN may not be enough. An organization admin controls which tool groups are available, must enable delete and manage tools for Jira, and must turn on API token authentication before anyone can use it. ### Has this Atlassian Rovo MCP guide been tested? Atlassian Rovo's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work. ## Sources - https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/ (checked 2026-11-05) - https://github.com/atlassian/atlassian-mcp-server (checked 2026-11-05) - https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/ (checked 2026-11-05) - https://registry.modelcontextprotocol.io/v0.1/servers/com.atlassian%2Fatlassian-mcp-server/versions/2.0.0 (checked 2026-11-05) - https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization (checked 2026-11-05) Guide JSON: https://github.com/apideck-libraries/mcp-connect/blob/626f6a146170ded34891b30dca3af26f09e07466/proposals/connection-guide/0.1/reviewed/guides/atlassian-mcp.json