← MCP

Atlassian Remote MCP Server（Jira/Confluence）Atlassian Remote MCP Server（Jira/Confluence）

Atlassian

MCPMCP 项目管理Project management wikiwiki JiraJira ConfluenceConfluence 远程托管Remote-hosted partial lifecycle: active 核验Checked 2026-10-30

Atlassian 官方 Remote MCP server：一个端点接 Jira+Confluence 两面——agent 搜需求、建 issue、写 wiki。OAuth 3LO 用户鉴权，可见面跟着账号权限走。

Atlassian's official Remote MCP server: one endpoint covers Jira + Confluence — agents search requirements, create issues, write wiki pages. OAuth 3LO user auth; visibility follows account permissions.

适合与不适合When to use it, when not to

适合：企业研发流的「需求→代码→文档」agent 闭环。不适合：要写审批流；自建 Data Center 版（支持状态未核验）。

Fits: the enterprise 'requirements → code → docs' agent loop. Not a fit: write approval flows; self-hosted Data Center (support unverified).

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Atlassian Pty Ltd.（澳大利亚）。Atlassian Pty Ltd. (Australia).
国内使用Direct access: 大陆可直连direct OK　atlassian.com 直连实测 200（2026-10-21）。atlassian.com measured 200 direct (2026-10-21).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它把 Jira/Confluence 能力（搜 issue、读写页面、查项目）包装成工具给 agent 用。
It calls no model itself — an interface implementation called by MCP clients. It wraps Jira/Confluence capabilities (searching issues, reading and writing pages, querying projects) as tools for agents.
运行位置Where it runs: 官方托管远程 server（产品页直抓 200）；单端点覆盖 Jira+Confluence 两产品面。
An official hosted remote server (product page direct-fetched 200); a single endpoint covers both the Jira and Confluence product surfaces.
本地文件Local files: 不碰本机文件系统——作用域是 Atlassian 云端站点（issues、pages）。
Never touches the local file system — the scope is Atlassian cloud sites (issues, pages).
关机后的任务Tasks after shutdown: 服务在 Atlassian 侧；请求-响应语义，无后台任务。
The service lives on Atlassian's side; request-response semantics, no background tasks.
工具与扩展Tools & extensions: Jira：搜/读/建/改 issue、查项目；Confluence：搜/读/建/改页面。完整清单以官方文档为准，未逐条清点。
Jira: search/read/create/update issues, query projects; Confluence: search/read/create/update pages. The complete inventory follows the official docs; it has not been enumerated item by item.
上下文与记忆Context & memory: 无 server 侧跨会话记忆——状态在站点本身。
No server-side cross-session memory — state lives on the sites themselves.
权限与限制Permissions & limits: OAuth 3LO 用户鉴权：agent 可见面=所连账号在站点的权限（含项目级限制）；写能力（建 issue/改页面）直接生效——按「它能替你改 wiki」设防。
OAuth 3LO user authorization: the agent-visible surface = the connected account's permissions on the site (including project-level restrictions); write capabilities (creating issues / editing pages) take effect directly — defend on the assumption "it can edit your wiki for you".
适合什么任务Best for: 适合：企业研发流里 agent 取 Jira 需求上下文、写 Confluence 文档。不适合：要写审批流；Data Center 自建版支持状态未核验。
Fits: agents in enterprise dev flows pulling Jira requirement context and writing Confluence docs. Not a fit: scenarios needing write-approval flows; Data Center self-hosted support status is unverified.
传输方式Transport: Streamable HTTP 远程托管（官方端点）；核验：产品页 200（2026-10-21）。具体端点 URL 以官方文档为准（未逐条核验）。
Streamable HTTP remote hosting (official endpoint); verified: product page 200 (2026-10-21). The concrete endpoint URL follows the official docs (not verified item by item).
认证机制Authentication: OAuth 3LO（用户登录授权）；scope 按产品分（Jira/Confluence 各自 scope 族）。
OAuth 3LO (user login authorization); scopes are split by product (separate scope families for Jira / Confluence).
权限范围Permission scope: 读面：issue/页面搜索读取；写面：建改 issue、建改页面。跟着账号权限走；无工具级审批层。
Read surface: issue/page search and reading; write surface: create/update issues, create/update pages. It follows the account's permissions; there is no tool-level approval layer.

头号误解Top misconception

把「连上」当「能看全站点」——可见面跟着账号与项目权限Assuming 'connected' means 'sees the whole site' — visibility follows account and project permissions
Data Center（自建版）支持状态未核验——别按 Cloud 口径推自建Assuming Data Center (self-hosted) support — unverified; do not extrapolate from Cloud
旧 developer.atlassian.com 概念页路径 404——现役入口在产品页与 changelog（直抓核验）The old developer.atlassian.com concept page 404s — the live entry points are the product page and changelog (direct-fetched)

未知项清单Known unknowns

端点 URL 与 scope 全表（未逐条核验）
Data Center 支持状态（未见官方说明）
工具全清单（未逐条清点）

The endpoint URL and the full scope table (not verified item by item)
Data Center support status (no official statement seen)
The complete tool inventory (not enumerated item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
docs	Atlassian · 官方 Remote MCP 产品页（2026-10-21 直抓核验）Atlassian · official Remote MCP product page (direct-fetched 2026-10-21)	https://www.atlassian.com/platform/remote-mcp-server
changelog	Atlassian · 开发者 changelog（changelog）Atlassian · developer changelog	https://developer.atlassian.com/changelog/
docs	Atlassian · 官方 MCP 发布公告（2025-06 首发线）Atlassian · official MCP launch announcement (2025-06 initial launch line)	https://developer.atlassian.com/blog/2025/06/atlassian-remote-mcp-server/

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.