From 4887717ed28a36b76289bd9e1f7de62532f3dd21 Mon Sep 17 00:00:00 2001 From: Juan Carracedo Date: Mon, 5 Oct 2026 10:14:11 +0200 Subject: [PATCH 1/3] feat(atlassian-jira): add Atlassian Jira plugin via Atlassian's official remote MCP server Connects ZCode to Jira and Confluence on Atlassian Cloud through Atlassian's hosted remote MCP server (https://mcp.atlassian.com/v1/mcp), authenticated with OAuth 2.1 on first use. Ships a jira skill covering JQL search, issue creation, transitions, and sprint summaries. Category: developer-tools. Version 0.1.0. English and Chinese READMEs, manifest and marketplace description_i18n in both locales. --- marketplace.json | 29 ++++++++++ plugins/atlassian-jira/.mcp.json | 10 ++++ .../atlassian-jira/.zcode-plugin/plugin.json | 22 ++++++++ plugins/atlassian-jira/README.md | 56 +++++++++++++++++++ plugins/atlassian-jira/README_CN.md | 56 +++++++++++++++++++ plugins/atlassian-jira/skills/jira/SKILL.md | 30 ++++++++++ 6 files changed, 203 insertions(+) create mode 100644 plugins/atlassian-jira/.mcp.json create mode 100644 plugins/atlassian-jira/.zcode-plugin/plugin.json create mode 100644 plugins/atlassian-jira/README.md create mode 100644 plugins/atlassian-jira/README_CN.md create mode 100644 plugins/atlassian-jira/skills/jira/SKILL.md diff --git a/marketplace.json b/marketplace.json index b988fe57..0ce8d019 100644 --- a/marketplace.json +++ b/marketplace.json @@ -740,6 +740,35 @@ "visualization" ], "icon": "https://cdn-zcode.z.ai/zcode/official-plugin/assets/obsidian/icon.png" + }, + { + "name": "atlassian-jira", + "displayName": "Atlassian Jira", + "displayName_i18n": { + "en": "Atlassian Jira", + "zh-CN": "Atlassian Jira" + }, + "source": "./plugins/atlassian-jira", + "description": "Connect ZCode to Jira and Confluence on Atlassian Cloud through Atlassian's official remote MCP server (Rovo): search issues with JQL, create, edit, transition, and comment on issues, with a guided Jira skill.", + "description_i18n": { + "en": "Connect ZCode to Jira and Confluence on Atlassian Cloud through Atlassian's official remote MCP server (Rovo): search issues with JQL, create, edit, transition, and comment on issues, with a guided Jira skill.", + "zh-CN": "通过 Atlassian 官方远程 MCP 服务器（Rovo）把 ZCode 接入 Atlassian Cloud 的 Jira 与 Confluence：支持 JQL 检索、创建、编辑、流转和评论 Issue，并附带 Jira 使用技能。" + }, + "version": "0.1.0", + "author": { + "name": "Juan Carracedo" + }, + "category": "developer-tools", + "keywords": [ + "jira", + "atlassian", + "confluence", + "mcp", + "issue-tracking", + "sprint", + "backlog", + "oauth" + ] } ] } diff --git a/plugins/atlassian-jira/.mcp.json b/plugins/atlassian-jira/.mcp.json new file mode 100644 index 00000000..2369b2f4 --- /dev/null +++ b/plugins/atlassian-jira/.mcp.json @@ -0,0 +1,10 @@ +{ + "mcpServers": { + "atlassian": { + "type": "http", + "url": "https://mcp.atlassian.com/v1/mcp", + "enabled": true, + "timeoutMs": 60000 + } + } +} diff --git a/plugins/atlassian-jira/.zcode-plugin/plugin.json b/plugins/atlassian-jira/.zcode-plugin/plugin.json new file mode 100644 index 00000000..5ced28b0 --- /dev/null +++ b/plugins/atlassian-jira/.zcode-plugin/plugin.json @@ -0,0 +1,22 @@ +{ + "name": "atlassian-jira", + "description": "Connect ZCode to Jira and Confluence on Atlassian Cloud through Atlassian's official remote MCP server (Rovo): search issues with JQL, create, edit, transition, and comment on issues, with a guided Jira skill.", + "description_i18n": { + "en": "Connect ZCode to Jira and Confluence on Atlassian Cloud through Atlassian's official remote MCP server (Rovo): search issues with JQL, create, edit, transition, and comment on issues, with a guided Jira skill.", + "zh-CN": "通过 Atlassian 官方远程 MCP 服务器（Rovo）把 ZCode 接入 Atlassian Cloud 的 Jira 与 Confluence：支持 JQL 检索、创建、编辑、流转和评论 Issue，并附带 Jira 使用技能。" + }, + "version": "0.1.0", + "author": { + "name": "Juan Carracedo" + }, + "keywords": [ + "jira", + "atlassian", + "confluence", + "mcp", + "issue-tracking", + "sprint", + "backlog", + "oauth" + ] +} diff --git a/plugins/atlassian-jira/README.md b/plugins/atlassian-jira/README.md new file mode 100644 index 00000000..f2a2d473 --- /dev/null +++ b/plugins/atlassian-jira/README.md @@ -0,0 +1,56 @@ +# Atlassian Jira + +Connect ZCode to **Jira** and **Confluence** on **Atlassian Cloud** through [Atlassian's official remote MCP server](https://developer.atlassian.com/change-log/blog/2025/07/01/mcp-server-beta/) (part of Rovo). No local server, no API token files: the plugin declares the hosted endpoint and ZCode handles OAuth 2.1 sign-in in the browser on first use. + +## What it gives you + +- **MCP server `atlassian`** — the hosted Atlassian endpoint, exposing tools to search issues with JQL, read, create, edit, and transition issues, add comments, and work with Confluence pages. +- **Skill `jira`** — guidance for the agent on Jira workflows: building explicit JQL, confirming project/issue type before creating, discovering valid transitions per workflow, and summarizing sprints. + +## Structure + +``` +atlassian-jira/ +├── .zcode-plugin/ +│ └── plugin.json # Plugin manifest +├── skills/ +│ └── jira/ +│ └── SKILL.md # Jira workflow guidance +├── .mcp.json # MCP server declaration (remote HTTP) +├── README.md +└── README_CN.md +``` + +## Requirements + +- An **Atlassian Cloud** site with Jira. Self-managed **Jira Server / Data Center** is not reachable through the remote MCP server; use a Jira REST API tool for those deployments. +- The user must have a Jira license on the site being queried. + +## MCP servers + +| Name | Type | Endpoint | Auth | +| --- | --- | --- | --- | +| `atlassian` | `http` (remote) | `https://mcp.atlassian.com/v1/mcp` | OAuth 2.1 via browser on first use | + +## Getting started + +1. Install the plugin from the ZCode plugin marketplace. +2. Open a new session. On first use, ZCode opens the browser to sign in to Atlassian and authorize the site. +3. Try a prompt such as: *"Search my open Jira issues assigned to me and summarize them by status."* + +## Privacy and security + +- **Network access**: the only network dependency is Atlassian's hosted MCP endpoint (`mcp.atlassian.com`). Issue data flows between ZCode and Atlassian; the plugin itself runs no local code. +- **Credentials**: the plugin stores no credentials. OAuth tokens are handled by the ZCode client and Atlassian's authorization server. +- **Third-party service**: the Atlassian Remote MCP Server is operated by Atlassian and subject to [Atlassian's terms](https://www.atlassian.com/legal/customer-agreement). The plugin declares its public endpoint and adds no wrapper code. + +## Troubleshooting + +- **401 / not authenticated**: open ZCode → Settings → MCP and check the `atlassian` server status; restart the session to retry the OAuth flow. +- **Connection timeout**: Atlassian Cloud can be slow to answer; raise `timeoutMs` in `.mcp.json`. +- **Empty results or no sites**: verify the site is authorized for AI/MCP access in the Atlassian administration settings and that the user has a Jira license there. +- **Endpoint changes**: if Atlassian revises the route, update `url` in `.mcp.json`; the current endpoint is documented on Atlassian's Remote MCP Server page. + +## License + +This plugin is distributed under the [Apache-2.0 license](../../LICENSE) of this repository. diff --git a/plugins/atlassian-jira/README_CN.md b/plugins/atlassian-jira/README_CN.md new file mode 100644 index 00000000..32d0565b --- /dev/null +++ b/plugins/atlassian-jira/README_CN.md @@ -0,0 +1,56 @@ +# Atlassian Jira + +通过 [Atlassian 官方远程 MCP 服务器](https://developer.atlassian.com/change-log/blog/2025/07/01/mcp-server-beta/)（Rovo 的一部分）把 ZCode 接入 **Atlassian Cloud** 上的 **Jira** 与 **Confluence**。无需本地服务进程，也不用手动管理 API Token：插件只声明托管端点，首次使用时由 ZCode 在浏览器中完成 OAuth 2.1 登录授权。 + +## 提供什么 + +- **MCP 服务器 `atlassian`** — Atlassian 托管端点，提供按 JQL 检索 Issue、读取、创建、编辑、流转、评论 Issue，以及操作 Confluence 页面等工具。 +- **技能 `jira`** — 为 Agent 提供的 Jira 工作流指引：构造明确的 JQL、创建前确认项目与 Issue 类型、按 workflow 发现可用流转，以及 Sprint 汇总。 + +## 目录结构 + +``` +atlassian-jira/ +├── .zcode-plugin/ +│ └── plugin.json # 插件清单 +├── skills/ +│ └── jira/ +│ └── SKILL.md # Jira 工作流指引 +├── .mcp.json # MCP 服务器声明（远程 HTTP） +├── README.md +└── README_CN.md +``` + +## 使用前提 + +- 一个启用了 Jira 的 **Atlassian Cloud** 站点。远程 MCP 服务器无法访问自建的 **Jira Server / Data Center**；这类部署请改用 Jira REST API 工具。 +- 用户在被查询的站点上需拥有 Jira 许可证。 + +## MCP 服务器 + +| 名称 | 类型 | 端点 | 认证 | +| --- | --- | --- | --- | +| `atlassian` | `http`（远程） | `https://mcp.atlassian.com/v1/mcp` | 首次使用时浏览器完成 OAuth 2.1 | + +## 快速开始 + +1. 在 ZCode 插件市场安装本插件。 +2. 打开新会话。首次使用时，ZCode 会打开浏览器登录 Atlassian 并授权站点。 +3. 试一试这样的提示词：“搜索分配给我的未关闭 Jira Issue，并按状态汇总。” + +## 隐私与安全 + +- **网络访问**：唯一的网络依赖是 Atlassian 托管的 MCP 端点（`mcp.atlassian.com`）。Issue 数据在 ZCode 与 Atlassian 之间传输；插件本身不运行任何本地代码。 +- **凭证**：插件不存储任何凭证。OAuth Token 由 ZCode 客户端与 Atlassian 授权服务器处理。 +- **第三方服务**：Atlassian Remote MCP Server 由 Atlassian 运营，受[其服务条款](https://www.atlassian.com/legal/customer-agreement)约束。插件仅声明其公开端点，未包含任何封装代码。 + +## 常见问题 + +- **401 / 未认证**：打开 ZCode → Settings → MCP 查看 `atlassian` 服务器状态；重启会话以重试 OAuth 授权。 +- **连接超时**：Atlassian Cloud 有时响应较慢；可在 `.mcp.json` 中调大 `timeoutMs`。 +- **结果为空或没有站点**：确认该站点已在 Atlassian 管理设置中允许 AI/MCP 访问，且用户在该站点拥有 Jira 许可证。 +- **端点变更**：如 Atlassian 调整路径，请更新 `.mcp.json` 中的 `url`；当前端点见 Atlassian Remote MCP Server 官方文档。 + +## 许可证 + +本插件遵循本仓库的 [Apache-2.0 许可证](../../LICENSE)。 diff --git a/plugins/atlassian-jira/skills/jira/SKILL.md b/plugins/atlassian-jira/skills/jira/SKILL.md new file mode 100644 index 00000000..d7fb7c33 --- /dev/null +++ b/plugins/atlassian-jira/skills/jira/SKILL.md @@ -0,0 +1,30 @@ +--- +name: jira +description: Work with Jira and Confluence on Atlassian Cloud through Atlassian's official remote MCP server (Rovo). Search issues with JQL, create, edit, and transition issues, add comments, summarize sprints and backlogs, and read Confluence pages. Use when the user mentions Jira, issue, ticket, sprint, backlog, Confluence, or Atlassian. +--- + +# Atlassian Jira (official Atlassian remote MCP server) + +This plugin brings the MCP tools of Atlassian's official remote server (`https://mcp.atlassian.com/v1/mcp`), exposed by Atlassian as part of Rovo. Tools are registered under the `mcp__atlassian__` prefix and cover Jira and Confluence: search, read, create, edit, transition, and comment. Check the exact tool names available in the current session before calling them; do not assume specific tool names. + +Respond in the user's language. + +## Requirements + +- An **Atlassian Cloud** account. The remote MCP server does not reach self-managed Jira Server / Data Center instances; for those, use the Jira REST API with an API token instead. +- The first connection triggers an **OAuth 2.1** flow: the client opens the browser to sign in to Atlassian and authorize access to the site. Without that authorization, tools fail with 401. + +## Typical workflows + +- **Search issues**: build an explicit JQL and pass it to the search tool. Examples: `assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC`, `project = ABC AND sprint in openSprints()`. Report key, summary, status, and assignee; never invent issues the search did not return. +- **Create an issue**: confirm project, issue type, summary, and description before creating. If the user did not give a project or type, ask, or look them up with the metadata tools instead of guessing IDs. +- **Transition**: list the transitions available on the issue and pick the one matching the user's request; do not hard-code transition IDs, they vary per workflow. +- **Comment and edit**: before updating fields, read the issue to learn current values and the format each field expects. +- **Sprint / status summaries**: combine JQL searches (sprint issues grouped by status, assignee, priority) with reads of individual issues when the user asks for detail. + +## Troubleshooting + +- **401 / not authenticated**: open ZCode → Settings → MCP and check the status of the `plugin:atlassian-jira:atlassian` server; restart the session to retry the OAuth flow. +- **Timeout**: Atlassian Cloud can be slow to answer; raise `timeoutMs` in `.mcp.json`. +- **Empty results or no sites**: verify the Atlassian site is authorized for the MCP server (Rovo/AI permissions in the site administration) and that the user has a Jira license on that site. +- **Endpoint 404**: if Atlassian changes the route, the current one is documented on their Remote MCP Server page; update `url` in `.mcp.json`. From d85dc5b3dcd65e48f4484dc72963ae58e8f17516 Mon Sep 17 00:00:00 2001 From: Juan Carracedo Date: Mon, 9 Nov 2026 15:16:13 +0100 Subject: [PATCH 2/3] chore(atlassian-jira): declare skills directory in plugin manifest Follow the current repo convention (as of 0cc58d6) of explicitly declaring "skills": "./skills" in plugin.json. --- plugins/atlassian-jira/.zcode-plugin/plugin.json | 1 + 1 file changed, 1 insertion(+) diff --git a/plugins/atlassian-jira/.zcode-plugin/plugin.json b/plugins/atlassian-jira/.zcode-plugin/plugin.json index 5ced28b0..f9678d6b 100644 --- a/plugins/atlassian-jira/.zcode-plugin/plugin.json +++ b/plugins/atlassian-jira/.zcode-plugin/plugin.json @@ -6,6 +6,7 @@ "zh-CN": "通过 Atlassian 官方远程 MCP 服务器（Rovo）把 ZCode 接入 Atlassian Cloud 的 Jira 与 Confluence：支持 JQL 检索、创建、编辑、流转和评论 Issue，并附带 Jira 使用技能。" }, "version": "0.1.0", + "skills": "./skills", "author": { "name": "Juan Carracedo" }, From 8387b74508ad6778fb95f90e2bdb0d1394a20738 Mon Sep 17 00:00:00 2001 From: Juan Carracedo Date: Mon, 9 Nov 2026 16:21:30 +0100 Subject: [PATCH 3/3] fix(atlassian-jira): use Atlassian MCP v2 endpoint mcp.atlassian.com/v2/mcp is the current recommended endpoint per Atlassian's docs (v1 -> v2 upgrade guide); v2 also exposes tools that v1 does not. Docs links updated from the July 2025 beta post to the official Remote MCP Server guide. --- plugins/atlassian-jira/.mcp.json | 2 +- plugins/atlassian-jira/README.md | 6 +++--- plugins/atlassian-jira/README_CN.md | 6 +++--- plugins/atlassian-jira/skills/jira/SKILL.md | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/plugins/atlassian-jira/.mcp.json b/plugins/atlassian-jira/.mcp.json index 2369b2f4..d1ddccd9 100644 --- a/plugins/atlassian-jira/.mcp.json +++ b/plugins/atlassian-jira/.mcp.json @@ -2,7 +2,7 @@ "mcpServers": { "atlassian": { "type": "http", - "url": "https://mcp.atlassian.com/v1/mcp", + "url": "https://mcp.atlassian.com/v2/mcp", "enabled": true, "timeoutMs": 60000 } diff --git a/plugins/atlassian-jira/README.md b/plugins/atlassian-jira/README.md index f2a2d473..69c01d3b 100644 --- a/plugins/atlassian-jira/README.md +++ b/plugins/atlassian-jira/README.md @@ -1,6 +1,6 @@ # Atlassian Jira -Connect ZCode to **Jira** and **Confluence** on **Atlassian Cloud** through [Atlassian's official remote MCP server](https://developer.atlassian.com/change-log/blog/2025/07/01/mcp-server-beta/) (part of Rovo). No local server, no API token files: the plugin declares the hosted endpoint and ZCode handles OAuth 2.1 sign-in in the browser on first use. +Connect ZCode to **Jira** and **Confluence** on **Atlassian Cloud** through [Atlassian's official remote MCP server](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/) (v2, part of Rovo). No local server, no API token files: the plugin declares the hosted endpoint and ZCode handles OAuth 2.1 sign-in in the browser on first use. ## What it gives you @@ -30,7 +30,7 @@ atlassian-jira/ | Name | Type | Endpoint | Auth | | --- | --- | --- | --- | -| `atlassian` | `http` (remote) | `https://mcp.atlassian.com/v1/mcp` | OAuth 2.1 via browser on first use | +| `atlassian` | `http` (remote) | `https://mcp.atlassian.com/v2/mcp` | OAuth 2.1 via browser on first use | ## Getting started @@ -49,7 +49,7 @@ atlassian-jira/ - **401 / not authenticated**: open ZCode → Settings → MCP and check the `atlassian` server status; restart the session to retry the OAuth flow. - **Connection timeout**: Atlassian Cloud can be slow to answer; raise `timeoutMs` in `.mcp.json`. - **Empty results or no sites**: verify the site is authorized for AI/MCP access in the Atlassian administration settings and that the user has a Jira license there. -- **Endpoint changes**: if Atlassian revises the route, update `url` in `.mcp.json`; the current endpoint is documented on Atlassian's Remote MCP Server page. +- **Endpoint changes**: if Atlassian revises the route, update `url` in `.mcp.json`; the current endpoint is documented in [Atlassian's Remote MCP Server guide](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/). ## License diff --git a/plugins/atlassian-jira/README_CN.md b/plugins/atlassian-jira/README_CN.md index 32d0565b..b5b4788d 100644 --- a/plugins/atlassian-jira/README_CN.md +++ b/plugins/atlassian-jira/README_CN.md @@ -1,6 +1,6 @@ # Atlassian Jira -通过 [Atlassian 官方远程 MCP 服务器](https://developer.atlassian.com/change-log/blog/2025/07/01/mcp-server-beta/)（Rovo 的一部分）把 ZCode 接入 **Atlassian Cloud** 上的 **Jira** 与 **Confluence**。无需本地服务进程，也不用手动管理 API Token：插件只声明托管端点，首次使用时由 ZCode 在浏览器中完成 OAuth 2.1 登录授权。 +通过 [Atlassian 官方远程 MCP 服务器](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/)（v2，Rovo 的一部分）把 ZCode 接入 **Atlassian Cloud** 上的 **Jira** 与 **Confluence**。无需本地服务进程，也不用手动管理 API Token：插件只声明托管端点，首次使用时由 ZCode 在浏览器中完成 OAuth 2.1 登录授权。 ## 提供什么 @@ -30,7 +30,7 @@ atlassian-jira/ | 名称 | 类型 | 端点 | 认证 | | --- | --- | --- | --- | -| `atlassian` | `http`（远程） | `https://mcp.atlassian.com/v1/mcp` | 首次使用时浏览器完成 OAuth 2.1 | +| `atlassian` | `http`（远程） | `https://mcp.atlassian.com/v2/mcp` | 首次使用时浏览器完成 OAuth 2.1 | ## 快速开始 @@ -49,7 +49,7 @@ atlassian-jira/ - **401 / 未认证**：打开 ZCode → Settings → MCP 查看 `atlassian` 服务器状态；重启会话以重试 OAuth 授权。 - **连接超时**：Atlassian Cloud 有时响应较慢；可在 `.mcp.json` 中调大 `timeoutMs`。 - **结果为空或没有站点**：确认该站点已在 Atlassian 管理设置中允许 AI/MCP 访问，且用户在该站点拥有 Jira 许可证。 -- **端点变更**：如 Atlassian 调整路径，请更新 `.mcp.json` 中的 `url`；当前端点见 Atlassian Remote MCP Server 官方文档。 +- **端点变更**：如 Atlassian 调整路径，请更新 `.mcp.json` 中的 `url`；当前端点见 [Atlassian Remote MCP Server 官方文档](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/)。 ## 许可证 diff --git a/plugins/atlassian-jira/skills/jira/SKILL.md b/plugins/atlassian-jira/skills/jira/SKILL.md index d7fb7c33..f19cfcb7 100644 --- a/plugins/atlassian-jira/skills/jira/SKILL.md +++ b/plugins/atlassian-jira/skills/jira/SKILL.md @@ -5,7 +5,7 @@ description: Work with Jira and Confluence on Atlassian Cloud through Atlassian' # Atlassian Jira (official Atlassian remote MCP server) -This plugin brings the MCP tools of Atlassian's official remote server (`https://mcp.atlassian.com/v1/mcp`), exposed by Atlassian as part of Rovo. Tools are registered under the `mcp__atlassian__` prefix and cover Jira and Confluence: search, read, create, edit, transition, and comment. Check the exact tool names available in the current session before calling them; do not assume specific tool names. +This plugin brings the MCP tools of Atlassian's official remote server (`https://mcp.atlassian.com/v2/mcp`), exposed by Atlassian as part of Rovo. Tools are registered under the `mcp__atlassian__` prefix and cover Jira and Confluence: search, read, create, edit, transition, and comment. Check the exact tool names available in the current session before calling them; do not assume specific tool names. Respond in the user's language.