[DonsWayo]

What user problem does this solve

ZCode has connectors for GitHub, GitLab, Alibaba Cloud, Lark, DingTalk and WeCom, but no Atlassian/Jira integration. This plugin connects ZCode to Jira (and Confluence) on Atlassian Cloud through Atlassian's official hosted remote MCP server (https://mcp.atlassian.com/v2/mcp), giving real issue tools (JQL search, create/edit/transition/comment) with OAuth 2.1 handled by the client on first use. No local server, no API tokens.

Visible behavior and how it was tested

• Install → open a session → browser opens for Atlassian OAuth → mcp__atlassian__* tools become available. Tested in ZCode Desktop (daily use): searching my open issues and summarizing by status returns real data.
• python3 scripts/validate.py → OK (27 plugins validated)
• python3 scripts/build_dist.py → builds atlassian-jira/0.1.0/plugin.zip
• git diff --check → clean

Version and marketplace registration

• New plugin atlassian-jira v0.1.0 registered in the root marketplace.json, category developer-tools.

Dependencies, network requests, permissions, and side effects

• Only network dependency is Atlassian's hosted MCP endpoint (mcp.atlassian.com); issue data flows between ZCode and Atlassian.
• No local code execution, no hooks, no credentials stored by the plugin (OAuth handled by the ZCode client and Atlassian's authorization server).
• Requires an Atlassian Cloud site (self-managed Server/Data Center is not reachable via the remote MCP).

Licensing / provenance

• Plugin code is new, contributed under the repo's Apache-2.0 license.
• The Atlassian Remote MCP Server is a third-party service operated by Atlassian; the plugin only declares its public endpoint, no wrapper code.

[panda920]

✅ Internal validation passed. A ZCode maintainer will review the change next; once merged it is published to the marketplace and this PR is closed automatically.

[jacksonliuyn]

Thanks for contributing this integration! Could you please confirm whether you've tested this plugin end to end in ZCode, including completing the Atlassian OAuth flow and successfully running a Jira tool call (for example, searching for or reading an issue)?

[DonsWayo]

Hi @jacksonliuyn — sorry, I missed your comment until now.

Yes, confirmed — I tested this plugin end to end in ZCode Desktop, which is my daily driver:

1. End-to-end install → OAuth: after installing, the first Jira tool call opens the browser for Atlassian's OAuth 2.1 consent (no API tokens involved), and on approval the mcp__atlassian__* tools become available in the session.
2. Real tool call: ran a JQL search for issues assigned to currentUser() and summarized them by status — real data from my Atlassian Cloud site.

I've also updated the branch meanwhile:

• Resolved the conflict with main (upstream added several plugins to marketplace.json); python3 scripts/validate.py → OK (53 plugins), and dist/plugins/atlassian-jira/0.1.0/plugin.zip builds.
• Added "skills": "./skills" to plugin.json, following the convention introduced in 0cc58d6.

Happy to run any specific scenario you'd like to see.

[DonsWayo]

Follow-up: I've switched the plugin to Atlassian's current v2 endpoint (https://mcp.atlassian.com/v2/mcp) — the v1 route I originally declared was the July 2025 beta one. Per Atlassian's v1 → v2 upgrade guide, v2 is the recommended endpoint and also exposes tools that v1 doesn't.

Updated in commit 8387b74:

• .mcp.json → url now points to https://mcp.atlassian.com/v2/mcp
• Docs links in both READMEs and the jira skill now point at the official Remote MCP Server guide instead of the beta announcement post

The end-to-end testing I described above was against Atlassian's hosted MCP server (same OAuth 2.1 flow); happy to re-run any specific scenario against v2.