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.

DimensionJira MCP ServerInteract with Jira using natural language to manage projects efficiently.Notion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS42 / 100 · D64 / 100 · C
Reliability6 / 208 / 20
Security and permissions8 / 2017 / 20
Maintenance6 / 2010 / 20
Documentation12 / 2016 / 20
Setup experience10 / 2013 / 20
Best for
  • Teams using Jira for project management
  • Users who want to manage tasks via natural language with AI assistants
  • Developers needing to automate common PM operations like assignment and status updates
  • 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 who do not use Jira
  • Scenarios requiring complex permission management
  • Developers who need direct API access without natural language interaction
  • 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
  • Read access to Jira projects, issues, and user information
  • Create, update, and delete issues and subtasks
  • Create issue links (dependencies)
  • Requires JIRA_HOST, JIRA_API_TOKEN or PAT, and JIRA_EMAIL for basic auth
  • 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
  • If API tokens are leaked, attackers can access and modify Jira data
  • Delete operations are irreversible and may cause data loss, especially when deleting subtasks
  • Misconfiguration may lead to permission issues or API rate limits
  • Dependent on Jira API version, subject to instance limitations
  • 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, CursorClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools119