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 CenterNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS60 / 100 · C64 / 100 · C
Reliability9 / 208 / 20
Security and permissions15 / 2017 / 20
Maintenance8 / 2010 / 20
Documentation14 / 2016 / 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
  • Teams and individuals who already manage docs/wikis in Notion and want AI clients (Claude Desktop, Cursor, etc.) to operate on that content directly
  • Developers who want to self-host a local MCP server rather than use a remote hosted option
  • Automation/agent workflows that need to query or update Notion database records programmatically
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 who want the standard-OAuth, zero-JSON-config install with active official support — Notion recommends its newer remote Notion MCP server for that
  • Users uncomfortable handing a Notion integration token to a locally-run LLM client
  • Use cases needing capabilities the integration deliberately excludes, such as deleting databases
  • Long-term production deployments that need guaranteed maintenance, given this repo may be sunset
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
  • A Notion internal integration token (NOTION_TOKEN or the Authorization value in OPENAPI_MCP_HEADERS), scoped by that integration's Capabilities (can be limited to read-only)
  • Access limited to the specific pages/databases explicitly connected to the integration, not the whole workspace
  • A separate bearer auth token when using the Streamable HTTP transport (--auth-token / AUTH_TOKEN)
  • Network access to the Notion API
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
  • If the integration is granted broad read/write capabilities and connected to many pages, that content is effectively exposed to the LLM, risking data leakage or unintended edits
  • Running with --unsafe-disable-auth removes bearer authentication on the HTTP transport, potentially making it reachable via DNS rebinding from pages a user visits — the README says to only use it on an isolated network
  • Multi-tenant token passthrough requires careful TLS/gateway configuration; misconfiguration risks leaking or misrouting Notion tokens between tenants
  • The README states this local server may be sunset in favor of the remote Notion MCP, and that issues/PRs here are not actively monitored, so long-term maintenance and security fixes are not guaranteed
  • Storing NOTION_TOKEN or OPENAPI_MCP_HEADERS directly in shared client config files risks leaking the secret
Supported clientsClaude Desktop, Claude CodeClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools09