Atlassian MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南

🛡️ Official✓ VerifiedHTTP + SSEOAuth 2.1🧩 MCP App🛡️ A+~781 tok23 tools·Online81ms·30 天在线率: 100%·上次拨测 12 分钟前

Atlassian 官方远程 MCP 服务器,覆盖 Jira 与 Confluence。通过 OAuth 2.1 授权后可在 Streamable HTTP 传输上搜索、创建工单与页面(保留旧版 SSE 端点)。

本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。

https://mcp.atlassian.com/v1/mcp
SSEhttps://mcp.atlassian.com/v1/sse
提供方
Atlassian ↗
分类
📋 项目管理与生产力
HTTP + SSEhttps://mcp.atlassian.com/v1/mcp
Legacy SSE endpoint
SSEhttps://mcp.atlassian.com/v1/sse
Install in Cursor →

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "atlassian": {
      "url": "https://mcp.atlassian.com/v1/mcp"
    }
  }
}

🧰 Atlassian MCP 工具与 Schema(23)

ToolSafetyDescriptionParameters
getAccessibleAtlassianResources
~40 tok
🟢 ReadList Atlassian cloud sites accessible to the user.—
getConfluenceSpaces
~30 tok
🟢 ReadList Confluence spaces.—
getConfluencePage
~31 tok
🟢 ReadGet a Confluence page by ID.—
getPagesInConfluenceSpace
~34 tok
🟢 ReadList pages in a Confluence space.—
getConfluencePageDescendants
~36 tok
🟢 ReadList descendants of a Confluence page.—
searchConfluenceUsingCql
~34 tok
🟢 ReadSearch Confluence content with CQL.—
getConfluencePageFooterComments
~35 tok
🟢 ReadList footer comments on a page.—
getConfluencePageInlineComments
~35 tok
🟢 ReadList inline comments on a page.—
createConfluencePage
~31 tok
🟠 WriteCreate a Confluence page.—
updateConfluencePage
~31 tok
🟠 WriteUpdate a Confluence page.—
createConfluenceFooterComment
~34 tok
🟠 WriteAdd a footer comment to a page.—
createConfluenceInlineComment
~35 tok
🟠 WriteAdd an inline comment to a page.—
getJiraIssue
~28 tok
🟢 ReadGet a Jira issue by key.—
searchJiraIssuesUsingJql
~32 tok
🟢 ReadSearch Jira issues with JQL.—
getVisibleJiraProjects
~32 tok
🟢 ReadList visible Jira projects.—
getJiraProjectIssueTypesMetadata
~37 tok
🟢 ReadList issue types available in a project.—
getJiraIssueTypeMetaWithFields
~36 tok
🟢 ReadGet field metadata for an issue type.—
createJiraIssue
~28 tok
🟠 WriteCreate a Jira issue.—
editJiraIssue
~30 tok
🟠 WriteEdit fields of a Jira issue.—
transitionJiraIssue
~34 tok
🟠 WriteTransition a Jira issue to a new status.—
lookupJiraAccountId
~31 tok
🟢 ReadLook up a Jira account ID.—
addCommentToJiraIssue
~32 tok
🟠 WriteAdd a comment to a Jira issue.—
getJiraIssueRemoteIssueLinks
~35 tok
🟢 ReadList remote links on a Jira issue.—

🛡️ 安全评级、质量与上下文 Token 审计

🛡️ 安全评级 A+上下文 Token 开销: ~781 tokens(该服务端 23 个工具定义注入每次系统提示词)

估算单次调用 Token 成本 →

  • No prompt-injection or hidden-character anomalies detected in tool descriptions
  • Streamable HTTP primary endpoint (current 2025-03-26 transport)
  • OAuth 2.1 with PKCE S256 enforced
  • Official first-party endpoint operated by the vendor
  • Manually verified by RemoteMCP.net

🔐 OAuth 2.1 与安全

认证方式
OAuth 2.1
动态客户端注册(DCR)
✅ 支持
PKCE S256
✅ 支持
Scopes
read:jira-workwrite:jira-workread:confluence-content.alloffline_access
受保护资源元数据
https://mcp.atlassian.com/.well-known/oauth-protected-resource
审计 OAuth 2.1 配置 →

📡 官方远程端点与传输协议

远程端点 https://mcp.atlassian.com/v1/mcp 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范),同时保留旧版 SSE 端点 https://mcp.atlassian.com/v1/sse 以兼容早期客户端。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。

接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。

🔐 认证与权限机制

认证方式为 OAuth 2.1。首次连接时客户端会收到 401 挑战并从 WWW-Authenticate 头解析 RFC 9728 受保护资源元数据,随后自动完成授权服务器发现(RFC 8414)、动态客户端注册(DCR)与 PKCE S256 浏览器授权流程——你只需在浏览器中点击一次授权,无需手工粘贴任何密钥。

🛡️ 上下文开销与安全审计

该服务端当前登记 23 个工具,全部定义合计约 781 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。

🧩 主流客户端快速接入

本站为 Atlassian MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 getAccessibleAtlassianResources、getConfluenceSpaces、getConfluencePage、getPagesInConfluenceSpace、getConfluencePageDescendants 等。

📖 Atlassian 详解

Atlassian MCP — Remote MCP Server

Atlassian's remote MCP covers the Rovo toolset across Jira and Confluence on Cloud. The primary endpoint speaks Streamable HTTP at /v1/mcp, with a legacy /v1/sse endpoint kept for older clients. OAuth 2.1 uses Atlassian's standard 3LO scopes, and access is bound to the Cloud sites you approve.

Official Atlassian MCP Endpoint & Transport Architecture

  • Primary endpoint (Streamable HTTP): https://mcp.atlassian.com/v1/mcp
  • Legacy SSE endpoint: https://mcp.atlassian.com/v1/sse
  • Transport: Streamable HTTP + legacy SSE

Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Atlassian MCP also keeps a legacy HTTP+SSE endpoint for clients pinned to the 2024 spec — always prefer the Streamable HTTP URL when your client supports it.

Authentication, Scopes & Permission Boundaries

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.

Of the 4 cataloged tools, 3 are read-only and 1 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.

Common Troubleshooting & Connection Tips

  • 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-Authenticate challenge.
  • Which URL should I use? Prefer https://mcp.atlassian.com/v1/mcp (Streamable HTTP). The SSE URL is only for older clients pinned to the pre-2025-03-26 spec.
  • "Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
  • Prefer /v1/mcp (Streamable HTTP); /v1/sse exists only for clients pinned to the legacy SSE transport.
  • Covers Atlassian Cloud sites; Data Center instances are not supported.

🚀 如何接入 Atlassian MCP 远程 MCP

  1. 获取远程端点 — 复制官方端点 https://mcp.atlassian.com/v1/mcp。
  2. 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL(见下方分客户端指南)。
  3. 授权并验证 — 完成浏览器 OAuth 授权后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。

🔌 Atlassian × 各客户端连接指南

❓ 常见问题

Atlassian MCP 远程 MCP 服务器是官方提供的吗?

本条目标记为「官方直营」。端点由 Atlassian 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。

如何在 Claude / Cursor 中连接 Atlassian MCP?

复制远程端点 https://mcp.atlassian.com/v1/mcp:Claude Code 执行 claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v1/mcp" } } }。首次调用会自动弹出 OAuth 2.1 授权页面。

连接时返回 401 或需要密钥怎么办?

401 是 OAuth 2.1 的正常挑战响应——客户端会依据 RFC 9728 元数据自动完成授权,无需手工处理。若授权流程中断,可用本站 OAuth 2.1 Debugger 定位 PRM / DCR / CORS 配置问题。

本地 stdio MCP 和这个远程 MCP 有什么区别?

本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 Atlassian 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。

🔗 同类远程 MCP 服务端