Atlassian MCP Server URL: Official Endpoint and Setup Guide

Atlassian MCP Server URL: Official Endpoint and Setup Guide

Quick Answer

The current official Streamable HTTP endpoint documented for the Atlassian Rovo MCP Server is:

https://mcp.atlassian.com/v1/mcp

This is Atlassian's hosted MCP service for connecting supported AI clients to Atlassian products through the Model Context Protocol.

If you are looking for the Atlassian MCP Server URL, do not use:

• your Jira or Confluence site URL
• a Jira REST API URL
• an OAuth authorization URL copied from a browser redirect
• the endpoint of the separate community mcp-atlassian project
• an old MCP endpoint copied from an outdated tutorial

Atlassian has changed its remote MCP configuration and authentication guidance over time. Before configuring a production integration, compare the endpoint and authentication method with the current official Atlassian documentation.

Official Atlassian MCP Server URL

Your Atlassian Cloud site URL is not an MCP server URL

For example:

https://yourcompany.atlassian.net

is the address of an Atlassian Cloud site. It should not be pasted into an MCP client's server URL field as a replacement for the hosted Atlassian MCP endpoint.

The same applies to Jira REST API endpoints. REST API URLs and MCP endpoints serve different protocols and use different request flows.

What Does the Atlassian MCP Server URL Connect To?

The endpoint at:

https://mcp.atlassian.com/v1/mcp

connects an MCP client to Atlassian's hosted Rovo MCP service.

The exact tools and operations available to a user can depend on the current Atlassian implementation, account permissions, enabled Atlassian products, administrator controls, and other service-specific requirements.

For that reason, do not rely on a static third-party list of Atlassian MCP tools.

After connecting successfully, inspect the tools exposed to your authenticated client and compare them with Atlassian's current documentation.

The basic connection flow is:

MCP Client
    |
    | HTTPS
    v
Atlassian Rovo MCP Server
    |
    | Authentication and authorization
    v
Available Atlassian MCP tools
    |
    | Existing user permissions and service controls
    v
Atlassian resources

A successful network connection does not automatically prove that authentication, authorization, MCP initialization, or tool discovery has completed successfully.

Current Atlassian MCP Endpoint vs Legacy SSE Endpoint

Older Atlassian MCP configurations can reference:

https://mcp.atlassian.com/v1/sse

This is the legacy SSE endpoint.

Current Atlassian documentation uses Streamable HTTP for new remote MCP configurations. The current endpoint is:

https://mcp.atlassian.com/v1/mcp

Do not blindly replace URLs in a working production integration.

Before migrating an existing configuration:

1. Identify the endpoint currently configured.
2. Identify the MCP client and its version.
3. Check the transport used by the client.
4. Check the authentication method.
5. Read Atlassian's current migration guidance.
6. Update the endpoint and client configuration together.
7. Re-authenticate if required.
8. Verify MCP initialization and tool discovery.

Changing only the URL can leave an integration broken if the client is still configured for an incompatible transport or authentication flow.

If your client connects initially but later loses the connection, see the MCP Failed to Reconnect to Atlassian troubleshooting guide.

Why You Find Different Atlassian MCP URLs Online

Searching for the Atlassian MCP Server URL can return different endpoint paths and configuration examples. There are several reasons.

Older Tutorials Reference the SSE Endpoint

Early Atlassian remote MCP configurations used the legacy SSE endpoint.

Older blog posts, forum answers, videos, cached pages, and configuration snippets can still reference:

https://mcp.atlassian.com/v1/sse

Do not assume that an endpoint is current because it appears in a highly ranked search result.

Authentication Guidance Has Changed

Different documentation versions can show different endpoint paths or client setup methods.

Always treat Atlassian's current documentation as the source of truth for:

• the server endpoint
• supported transports
• authentication methods
• client-specific configuration
• migration requirements

The Official Server and Community Projects Are Different

The official Atlassian Rovo MCP Server is a hosted service maintained by Atlassian.

Projects such as mcp-atlassian are separate implementations. They can use different:

• server addresses
• transports
• authentication methods
• installation procedures
• configuration formats
• tools

Never copy configuration from one implementation into another without verifying that the instructions apply to the server you are actually using.

Atlassian Cloud URLs Are Not MCP Endpoints

A Jira or Confluence site URL can look like:

https://yourcompany.atlassian.net

That URL identifies your Atlassian Cloud site. It is not the hosted Atlassian Rovo MCP Server URL.

How to Configure the Atlassian MCP Server URL

The exact setup procedure depends on the MCP client.

Do not assume that every MCP client uses the same JSON structure, CLI command, transport name, or authentication flow.

Before adding the server:

1. Update the MCP client to a currently supported version.
2. Open Atlassian's official client setup documentation.
3. Find the instructions for your specific client.
4. Copy the current endpoint and configuration format.
5. Complete the documented authentication flow.
6. Verify the server connection.
7. Confirm MCP initialization succeeds.
8. Inspect the tools actually exposed to the client.
9. Run a low-risk test operation.

The current Atlassian Streamable HTTP endpoint is:

https://mcp.atlassian.com/v1/mcp

Client-specific examples below intentionally avoid unverified configuration snippets.

Atlassian MCP Server URL for Cursor

When configuring Atlassian MCP in Cursor, first verify that your Cursor version supports the remote MCP configuration method documented by Atlassian.

Use the current Atlassian endpoint:

https://mcp.atlassian.com/v1/mcp

Then follow the exact configuration and authentication procedure in the current Atlassian and Cursor documentation.

After adding the server, verify:

• the configured URL is correct
• Cursor can reach the remote endpoint
• the expected authentication flow completes
• MCP initialization succeeds
• Atlassian tools appear after connection
• a low-risk tool call succeeds

If Cursor reports a general connection failure, see Cursor MCP Server Failed to Connect.

Do not add a local proxy, bridge, or wrapper unless the current documentation for your Cursor version explicitly requires one.

Atlassian MCP Server URL for Claude Code

Claude Code supports MCP server integrations, but its CLI syntax and remote-server configuration behavior can change between releases.

Use the Atlassian endpoint documented for the current integration:

https://mcp.atlassian.com/v1/mcp

Copy the exact setup command from current Atlassian or Claude Code documentation.

After configuration:

1. Confirm the server appears in Claude Code's MCP configuration.
2. Complete the documented authentication flow.
3. Check the connection state.
4. Verify initialization completes.
5. Inspect available Atlassian tools.
6. Run a low-risk operation.

Avoid copying commands from old tutorials without checking the current CLI documentation.

Atlassian MCP Server URL for Claude Desktop

Claude Desktop configuration can differ from Claude Code.

Do not assume that a configuration snippet written for Claude Code, Cursor, VS Code, or another MCP client will work in Claude Desktop.

Check the current Atlassian client setup documentation and current Claude Desktop MCP documentation before choosing between:

• native remote MCP support
• a documented connector flow
• a documented compatibility bridge

Do not install mcp-remote solely because an old tutorial says it is required. If a compatibility bridge is required for your client version, use only the setup documented by Atlassian or the client maintainer.

Atlassian MCP Server URL for VS Code

VS Code MCP support can depend on the current VS Code release and the AI tooling being used.

Use:

https://mcp.atlassian.com/v1/mcp

as the Atlassian endpoint only when following the current official setup instructions.

Verify:

• the current configuration file location
• the required server configuration schema
• the supported transport
• the authentication procedure
• whether additional extensions or features are required

Do not paste a configuration object from Cursor or another client into VS Code without verifying the current VS Code MCP schema.

Atlassian MCP Server URL for Windsurf, Codex, and Other Clients

Client support and configuration formats change over time.

For Windsurf, Codex, and other MCP clients:

1. Check Atlassian's current list of supported clients.
2. Check the MCP client's official remote-server documentation.
3. Confirm support for the transport required by Atlassian.
4. Confirm support for Atlassian's documented authentication flow.
5. Use the current Atlassian endpoint.
6. Follow the client's exact configuration syntax.
7. Verify initialization and tool discovery after connecting.

Do not invent or adapt configuration formats from another client. A server URL alone is not enough to prove compatibility.

Endpoint URL vs Authentication Method

The MCP endpoint and authentication method are related configuration details, but they are not interchangeable.

Do not modify the endpoint path because:

• OAuth did not start
• authentication failed
• a token expired
• another tutorial shows a different URL

Instead:

1. Verify the endpoint against current Atlassian documentation.
2. Identify the authentication method documented for your client.
3. Inspect the complete client error.
4. Inspect the HTTP response status when available.
5. Check whether MCP initialization reached the authentication stage.
6. Follow Atlassian's current authentication troubleshooting guidance.

If your client reports an OAuth discovery problem, see MCP Failed to Discover OAuth Metadata.

Official Atlassian Rovo MCP Server vs Community mcp-atlassian

These are separate implementations.

The most important rule is simple: do not mix configuration instructions between the official hosted Atlassian server and community MCP implementations. Before troubleshooting, identify which server you are actually running.

Common Atlassian MCP Server URL Errors

HTTP status codes identify the response class. They do not, by themselves, prove the exact root cause.

Always inspect:

• the complete response
• client logs
• server-provided error details
• authentication state
• current official documentation

How to Verify the Atlassian MCP Server URL

Do not treat opening an MCP endpoint in a normal browser tab as a complete MCP connectivity test.

A browser request does not reproduce:

• MCP initialization
• protocol negotiation
• authentication behavior
• client headers
• session handling
• tool discovery

Use this verification process instead.

1. Confirm the Endpoint

Compare the configured URL with current Atlassian documentation.

For current Streamable HTTP configurations:

https://mcp.atlassian.com/v1/mcp

Check for:

• incorrect domain
• outdated path
• copied Jira or Confluence URL
• REST API URL
• legacy endpoint

2. Confirm Client Support

Verify that your MCP client supports the transport and authentication method required by the current Atlassian integration.

3. Complete Authentication

Follow the authentication flow documented for your specific MCP client.

Do not assume that all clients start authentication in the same way.

4. Verify MCP Initialization

A reachable HTTP endpoint is not enough.

Confirm that the MCP client completes initialization successfully and keeps the server connection in the expected state.

5. Inspect Discovered Tools

Inspect the tools exposed to the authenticated client.

Do not rely on a hardcoded third-party list of expected tools.

6. Run a Low-Risk Test Operation

Choose a read-only or otherwise low-risk operation available to your authenticated client.

Confirm:

• the tool call reaches the server
• authorization succeeds
• the expected result is returned
• no repeated connection or authentication errors appear

7. Use an Independent MCP Diagnostic Tool When Appropriate

The official MCP Inspector and MCPForge Test MCP Server are separate tools.

• Use the official MCP Inspector when you need protocol-level inspection supported by that tool.
• Use MCPForge Test MCP Server when its supported tests match the server and transport you are validating.

Do not describe MCPForge Test MCP Server as the official MCP Inspector.

For a detailed MCP Inspector guide, see MCP Inspector: Complete Guide.

Atlassian MCP Server URL Troubleshooting Checklist

If the Atlassian MCP Server URL is configured but the connection still fails, check:

• The endpoint matches current official Atlassian documentation.
• You are not using an Atlassian Cloud site URL as the MCP endpoint.
• You are not using a Jira REST API URL as the MCP endpoint.
• You are not following an outdated SSE tutorial for a new configuration.
• The MCP client version supports the required remote transport.
• The client is configured using its current documented schema.
• The documented authentication flow completed successfully.
• Client logs do not show authentication discovery failures.
• Client logs do not show initialization failures.
• A corporate proxy, firewall, VPN, or network policy is not blocking the connection.
• The authenticated Atlassian account has permission to perform the requested operation.
• Tools are discovered after successful initialization.
• A low-risk test tool call succeeds.

If the client initially connects but later loses the connection, use the MCP Failed to Reconnect to Atlassian guide.

For broader MCP connection failures, see MCP Server Failed to Connect.

Summary

The current Atlassian MCP Server URL for Streamable HTTP configurations is:

https://mcp.atlassian.com/v1/mcp

When configuring the official Atlassian Rovo MCP Server:

• use the endpoint documented by Atlassian
• do not substitute a Jira or Confluence site URL
• do not use REST API URLs as MCP endpoints
• avoid copying legacy SSE configurations into new setups
• verify the exact setup procedure for your MCP client
• complete the documented authentication flow
• confirm MCP initialization
• inspect the tools actually exposed to your client
• test a low-risk operation before relying on the integration

If the URL is correct but authentication fails, investigate the authentication layer instead of changing endpoint paths.

If the server connects but later loses the session, use the MCP Failed to Reconnect to Atlassian guide.

If the client reports OAuth metadata discovery failures, see MCP Failed to Discover OAuth Metadata.

Official Sources

Before publishing or updating this article, verify the endpoint, authentication method, migration guidance, and client-specific configuration against the current primary sources:

• Atlassian Support — Getting started with the Atlassian Rovo MCP Server
• Atlassian Support — Setting up MCP clients
• Atlassian Support — Atlassian Rovo MCP Server authentication documentation
• Model Context Protocol specification — Transports and lifecycle documentation

Client-specific setup examples should also be checked against the current official documentation of the client being configured.

Do not treat third-party tutorials, copied configuration snippets, search result summaries, or cached documentation as the source of truth for Atlassian MCP endpoint configuration.