← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGoogle Workspace MCPControl Google Workspace with natural language.Notion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS56 / 100 · C64 / 100 · C
Reliability8 / 208 / 20
Security and permissions10 / 2017 / 20
Maintenance12 / 2010 / 20
Documentation14 / 2016 / 20
Setup experience12 / 2013 / 20
Best for
  • Individuals and teams needing access to several Google Workspace services.
  • Developers deploying by tool tier, service, or permission scope.
  • Organizations needing self-hosted, multi-user OAuth 2.1, or container deployments.
  • Developers who want to call MCP tools through a CLI.
  • 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 requiring a server maintained by Google.
  • Users with only a personal @gmail.com account who need Google Chat.
  • Users unwilling to configure Google Cloud OAuth credentials or APIs.
  • Applications seeking unauthorized access to Google Workspace data.
  • 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 Google Cloud OAuth client credentials.
  • OAuth scopes depend on the enabled services and tools.
  • Supports read-only scopes, per-service granular permissions, and full access.
  • Write tools for Drive, Gmail, and other services require corresponding write permissions.
  • Google Chat requires a configured Chat app and a Google Workspace account.
  • Optional service-account mode requires service-account credentials and domain-wide delegation.
  • 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
  • Full tools and write scopes may allow modifying, sending, deleting, or sharing user data.
  • For public deployments, unrestricted dynamic-client redirect URIs can create a phishing risk.
  • Stdio is a legacy fallback; OAuth 2.1 is recommended for remote or shared deployments.
  • Local attachments and credential stores write to configured local directories; stateless mode avoids file writes.
  • Google API quotas, OAuth consent configuration, and account permissions may limit functionality.
  • The Chat API is unavailable for personal Gmail accounts.
  • 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, VS Code, LM StudioClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools299