Atlassian MCP vs FlyDocs
Atlassian MCP is a plugin bundle for AI coding tools published by atlassian. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). FlyDocs is an MCP server published by flydocs.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Atlassian MCP |  FlyDocs |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: eb9a595 Forks (GitHub): 140 Stars (GitHub): 1 090 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 2.0.0 Forks (GitHub): 140 Stars (GitHub): 1 090 Not marked · First seen |
Listed Version: 1.3.23 Downloads/month (npm): 2 436 Downloads/week (npm): 350 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 94a3043 Forks (GitHub): 140 Stars (GitHub): 1 090 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Atlassian MCP | FlyDocs |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 090 | No figure on GitHub |
| Forks (GitHub) (differs) | 140 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.atlassian.com/v2/mcp) | On your machine (@flydocs/cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/atlassian/atlassian-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 24 h ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Atlassian MCP
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
FlyDocs
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
How to run each
Atlassian MCP As a Claude Code plugin
/plugin install atlassian@claude-plugins-officialFlyDocs As a local MCP server: npm package
claude mcp add --transport stdio flydocs -- npx -y @flydocs/cli mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Atlassian MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Atlassian MCP · What it can do: FlyDocs · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.