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.

DimensionAsana MCP ServerConnect Asana with MCP to manage tasks, projects, comments, and tags.Notion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS41 / 100 · D64 / 100 · C
Reliability4 / 208 / 20
Security and permissions7 / 2017 / 20
Maintenance5 / 2010 / 20
Documentation12 / 2016 / 20
Setup experience13 / 2013 / 20
Best for
  • Teams that want to integrate Asana into their AI assistant workflow to operate tasks and projects via natural language.
  • Developers and project managers who need quick access to and modification of Asana data.
  • Teams that want to unify multiple tools via the MCP protocol.
  • 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 need to interact with Asana.
  • Organizations highly sensitive about data privacy who are uncomfortable with Asana data being processed by third-party servers (though this server runs locally).
  • Scenarios requiring advanced admin privileges (e.g., user management, workspace settings) not supported by this server.
  • 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 ASANA_ACCESS_TOKEN environment variable with read/write permissions to Asana API (depending on token scope).
  • When READ_ONLY_MODE=true, all write operations are disabled.
  • 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 leakage risk: if the access token is leaked, an attacker may read or modify Asana data. Store the token securely.
  • Accidental modifications: AI might execute delete or update operations unintentionally. It is recommended to test in a sandbox or enable READ_ONLY_MODE.
  • Data privacy: the server is only a bridge, but Asana data will be processed by the MCP client; consider the client's data handling.
  • 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 Code, CodexClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools419