Atlassian Remote MCP Server (Jira & Confluence)
Atlassian's hosted MCP (mcp.atlassian.com) gives agents Jira issue management and Confluence knowledge access across your Cloud sites, authorized per user via OAuth 2.1.
- Provider
- Atlassian โ
- Categories
- ๐ Project Management & Productivity
ไธญๆ็ฎไป
Atlassian ๅฎๆน่ฟ็จ MCP ๆๅกๅจ๏ผ่ฆ็ Jira ไธ Confluenceใ้่ฟ OAuth 2.1 ๆๆๅๅฏๅจ SSE ไผ ่พไธๆ็ดขใๅๅปบๅทฅๅไธ้กต้ขใ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"atlassian": {
"url": "https://mcp.atlassian.com/v1/sse"
}
}
}claude mcp add --transport sse atlassian https://mcp.atlassian.com/v1/sse
Or add to .vscode/mcp.json:
{
"servers": {
"atlassian": {
"type": "sse",
"url": "https://mcp.atlassian.com/v1/sse"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.atlassian.com/v1/sse - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"atlassian": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.atlassian.com/v1/sse"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"atlassian": {
"serverUrl": "https://mcp.atlassian.com/v1/sse"
}
}
}๐งฐ Tools exposed by Atlassian MCP (4)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search_jira_issues | ๐ข Read | Search Jira issues with JQL or text across accessible sites. | jql*: stringcloudId: string |
| create_jira_issue | ๐ Write | Create a Jira issue in a project. | projectKey*: stringsummary*: stringissueType: stringdescription: string |
| get_confluence_page | ๐ข Read | Retrieve a Confluence page's content. | pageId*: stringcloudId: string |
| search_confluence | ๐ข Read | Search Confluence content with CQL or text. | cql*: string |
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
read:jira-workwrite:jira-workread:confluence-content.alloffline_access- Protected resource metadata
- https://mcp.atlassian.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Guide
Atlassian MCP โ Remote MCP Server
Atlassian's remote MCP covers the Rovo toolset across Jira and Confluence on Cloud. It currently speaks the legacy HTTP+SSE transport only โ clients must support SSE, and in Claude Code that means claude mcp add --transport sse. OAuth 2.1 uses Atlassian's standard 3LO scopes, and access is bound to the Cloud sites you approve.
Endpoint & Transport
- Endpoint URL:
https://mcp.atlassian.com/v1/sse - Transport: HTTP+SSE (legacy SSE transport)
Authentication
Atlassian MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Available Tools (4)
| Tool | Safety | Description |
|---|---|---|
search_jira_issues |
read | Search Jira issues with JQL or text across accessible sites. |
create_jira_issue |
write | Create a Jira issue in a project. |
get_confluence_page |
read | Retrieve a Confluence page's content. |
search_confluence |
read | Search Confluence content with CQL or text. |
Connect in 30 Seconds
Claude Code โ one command:
claude mcp add --transport sse atlassian https://mcp.atlassian.com/v1/sse
Cursor โ add to ~/.cursor/mcp.json:
{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v1/sse" } } }
VS Code โ add to .vscode/mcp.json:
{ "servers": { "atlassian": { "type": "sse", "url": "https://mcp.atlassian.com/v1/sse" } } }
Claude Desktop & stdio clients โ bridge with mcp-remote:
{ "mcpServers": { "atlassian": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/sse"] } } }
On first connect your client opens a browser OAuth consent screen โ approve it and tools become available immediately.
Troubleshooting
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - Client says "unsupported transport" โ this endpoint only speaks the legacy SSE transport. Use a client with SSE support (Claude Code:
claude mcp add --transport sse) or bridge it withmcp-remote. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - SSE-only endpoint โ clients that only implement Streamable HTTP cannot connect.
- Covers Atlassian Cloud sites; Data Center instances are not supported.
๐ How to Connect
- Copy the Atlassian MCP endpoint URLThe remote endpoint is https://mcp.atlassian.com/v1/sse.
- Add it to your MCP clientClaude Code:
claude mcp add --transport sse atlassian https://mcp.atlassian.com/v1/sse. Cursor: add"atlassian": { "url": "https://mcp.atlassian.com/v1/sse" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Atlassian consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.atlassian.com/v1/sse into remotemcp.net/inspector, run initialize and tools/list, and confirm Atlassian MCP's 4 tools respond.
โ FAQ
What is the Atlassian MCP remote MCP endpoint?
The primary endpoint is https://mcp.atlassian.com/v1/sse. It is an official first-party server operated by Atlassian, speaking the HTTP+SSE (legacy SSE transport) transport.
How do I authenticate with Atlassian MCP?
Atlassian MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Atlassian MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Atlassian MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport sse atlassian https://mcp.atlassian.com/v1/sse`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge. Note this server only offers the SSE transport, so the client must support SSE.
What tools does Atlassian MCP expose?
4 tools are cataloged in this directory โ including `search_jira_issues`, `create_jira_issue`, `get_confluence_page` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
[](https://remotemcp.net/servers/atlassian)
[](https://remotemcp.net/inspector?url=https%3A%2F%2Fmcp.atlassian.com%2Fv1%2Fsse)
Related Servers
Notion's official hosted MCP server. Agents can search your workspace, read and create pages, and query databases over Streamable HTTP or SSE.
Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.
Asana's official remote MCP server. Agents can search tasks, create work items and read project structure over the SSE transport with OAuth.
Intercom's official remote MCP server for customer support data. Agents can search conversations, look up contacts and reply to threads over OAuth.