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.

DimensionKeep MCP ServerMCP server for Google Keep, enabling note management and automation.Microsoft 365 MCP ServerAn MCP server for interacting with Microsoft 365 and Office services through the Graph API.
FMRS60 / 100 · C61 / 100 · C
Reliability10 / 208 / 20
Security and permissions12 / 2013 / 20
Maintenance12 / 2010 / 20
Documentation14 / 2016 / 20
Setup experience12 / 2014 / 20
Best for
  • Personal knowledge management
  • Note automation
  • AI workflows tightly integrated with Google Keep
  • Developers who want to integrate Microsoft 365 data into AI assistants or custom applications.
  • Scenarios requiring unified access across multiple services (email, calendar, files, Teams, etc.).
  • Lightweight solutions to interact with Graph API via MCP protocol.
Not for
  • Environments requiring high security without sharing email tokens
  • Users without a Google account
  • Advanced features requiring full official API support (e.g., audio notes)
  • Highly secure enterprise production environments (requires careful scope management and deployment complexity).
  • Admin tasks requiring Microsoft 365 admin permissions (like security alerts, audit logs) — consider companion project ms-365-admin-mcp-server.
  • Environments without Node.js.
  • Support for non-Microsoft clouds like GCC High (only Global and China 21Vianet currently).
Required permissions
  • Requires access to Google account email and master token for authentication
  • Can read/write notes, labels, collaborators, and media; scope depends on token permissions and UNSAFE_MODE
  • Requires Microsoft Graph API permissions, dynamically requested based on enabled tools. Examples: User.Read, Mail.Read, Files.Read.
  • Organization mode (--org-mode) requires additional Graph permissions for Teams, SharePoint, etc. (e.g., Sites.Read.All).
  • Shared mailbox access requires delegated Mail.Read.Shared or Mail.Send.Shared scopes.
  • Use --allowed-scopes to restrict tool exposure; --extra-scopes to add extra scopes. Note: --allowed-scopes only narrows, never expands permissions.
Risks and side effects
  • Master token leakage could lead to unauthorized access to account data
  • Default safety mechanism (keep-mcp label) may limit modification of non-server notes; enabling UNSAFE_MODE increases risk
  • Destructive operations like deletion may be irreversible; use with caution
  • Token security: File-based token storage may be exposed; use OS credential storage or secure custom paths.
  • Overly broad permissions: default requests all scopes implied by tools; use allowed-scopes or tool filtering to limit.
  • Multi-tenant token risk: With default 'common' tenant, personal account refresh tokens may be rejected as of June 2026, causing session expiry.
  • Third-party project risk: Not officially maintained, potentially less stable than official solutions.
  • HTTP mode OAuth setup complexity: Requires correct Azure AD app registration and redirect URIs.
Supported clientsClaude Desktop, Cursor, Cline, Codex, GooseClaude Desktop, Open WebUI
Tools2310