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.

DimensionMCP Atlassian ServerMCP server connecting AI assistants to Jira and ConfluenceNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS54 / 100 · D64 / 100 · C
Reliability8 / 208 / 20
Security and permissions8 / 2017 / 20
Maintenance14 / 2010 / 20
Documentation13 / 2016 / 20
Setup experience11 / 2013 / 20
Best for
  • Developers who use Jira and Confluence daily with Cline
  • Individuals wanting to integrate Atlassian into AI workflows without context switching
  • MCP-compatible client users seeking quick Atlassian integration
  • 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
  • Teams requiring enterprise-grade official support or Atlassian-maintained assurance
  • Users without an MCP-compatible client
  • High-compliance environments needing strict centralized token governance
  • 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 an Atlassian API token that inherits all permissions of its creator
  • Tools can perform create, update, and delete mutations on Jira and Confluence data
  • Runs locally and needs access to Atlassian cloud APIs
  • 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
  • The API token inherits all of the creator's permissions, so a leak is high-impact
  • Never ask LLMs to analyze config files containing your token
  • Third-party, non-official project; Atlassian API changes may require maintenance
  • AI-driven mutations (deleting pages, transitioning issues) risk unintended changes
  • 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 clientsCline, Claude Desktop, CursorClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools09