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 Teams ServerRead, post, and reply to Microsoft Teams messages via MCP.Notion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS59 / 100 · C64 / 100 · C
Reliability9 / 208 / 20
Security and permissions12 / 2017 / 20
Maintenance15 / 2010 / 20
Documentation13 / 2016 / 20
Setup experience10 / 2013 / 20
Best for
  • Teams or organizations that have already completed Microsoft Teams and Azure/Entra ID app registration
  • Scenarios where an AI agent needs to post and reply to messages directly in Teams channels
  • Developers on the uv/Python stack who are comfortable self-hosting or using the official Docker image
  • 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
  • Individuals without a Microsoft 365/Teams account or unable to register an Entra ID app
  • Use cases needing 1:1 chat, meetings, or calls — not described as supported features
  • Users who want zero-configuration setup without handling OAuth client secrets and other sensitive credentials
  • 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
  • Microsoft Entra ID application ID and client secret (TEAMS_APP_ID / TEAMS_APP_PASSWORD)
  • Tenant configuration (TEAMS_APP_TYPE, and TEAMS_APP_TENANT_ID for SingleTenant setups)
  • Target MS Teams Team ID and Channel ID (TEAM_ID / TEAMS_CHANNEL_ID)
  • The registered app needs permission to read and post/reply to messages in the target channel
  • 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
  • TEAMS_APP_PASSWORD is a client secret; if leaked it could let an attacker impersonate the app and access Teams data, so environment variables and .env files must be protected
  • The server can read the full message history of a channel, potentially exposing sensitive channel content to the connected LLM or agent
  • The server can actively post or reply in the channel on the app's behalf, so misconfiguration or a bad prompt could send unintended messages to real users
  • 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, Cursor, Zed, GitHub Copilot CLI
Tools09