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.

DimensionTrello MCP ServerManage Trello boards, lists, and cards through Claude and other MCP clients.Notion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS47 / 100 · D64 / 100 · C
Reliability6 / 208 / 20
Security and permissions8 / 2017 / 20
Maintenance7 / 2010 / 20
Documentation14 / 2016 / 20
Setup experience12 / 2013 / 20
Best for
  • Individuals or teams already using Trello for task management who want to manipulate cards and lists conversationally via Claude Desktop or Cursor
  • Developers who want quick Trello access from Claude Desktop or any SSE-capable MCP client
  • 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 need to create, rename, or delete entire boards (not supported)
  • Users without a Trello API Key/Token or without access to the Trello Power-Up admin page
  • Scenarios requiring official Trello/Atlassian support or enterprise-grade security auditing
  • 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
  • A Trello API Key and Token (account-level access to read/write boards, lists, cards, and checklists the account can access)
  • Local .env file storing credentials in plaintext
  • Network access to call the Trello API, and (in SSE mode) an open local HTTP port
  • 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
  • API Key and Token are stored in plaintext in the .env file — leakage grants full control over the Trello account
  • Delete/archive operations on lists, cards, checklists, and checklist items are irreversible
  • SSE mode exposes a local HTTP endpoint; the README does not mention any built-in authentication for it
  • This is a community-maintained third-party server, not reviewed or endorsed by Trello/Atlassian
  • 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
Tools09