M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAtlassian Dc MCP JiraMCP server for Atlassian Jira Data CenterAtlassian Rovo MCP ServerSecurely connect Atlassian Cloud to AI tools.
FMRS60 / 100 · C66 / 100 · C
Reliability9 / 208 / 20
Security and permissions15 / 2015 / 20
Maintenance8 / 2015 / 20
Documentation14 / 2015 / 20
Setup experience14 / 2013 / 20
Best for
  • Organizations using Atlassian Jira Data Center
  • Teams that want to manage Jira issues via AI assistants
  • Users needing on-premise or private integration with Jira
  • Developers, content creators, and project teams using Atlassian Cloud
  • Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
  • Users who need natural-language search, write, and cross-product workflows
Not for
  • Users of Jira Cloud (non-Data Center)
  • Those requiring official support or warranty
  • Users without a Jira Data Center instance or API token
  • Users without an Atlassian Cloud site or relevant product permissions
  • Deployments requiring a self-hosted MCP server
  • Users unwilling to grant an AI client access to Atlassian data or actions
  • Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
Required permissions
  • Requires a Jira Personal Access Token (PAT)
  • Permissions depend on token scopes configured in Jira
  • Typically needs read permissions for viewing issues and write permissions for creating
  • Jira and Confluence provide read, write, and search permission groups
  • Jira Service Management provides read and write access through API tokens only
  • Bitbucket Cloud provides read and write access through scoped API tokens only
  • Compass is available through OAuth 2.1 only
  • The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
  • Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
Risks and side effects
  • Token could be leaked if stored in plain text config files
  • Community-maintained project may lack timely security updates
  • Overprivileged PATs could pose risks to the Jira instance
  • AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
  • Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
  • Use least privilege, scoped tokens, and minimal project or workspace access
  • Require human confirmation for high-impact or destructive actions and monitor audit logs
Supported clientsClaude Desktop, Claude CodeOpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote
Tools00