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.

DimensionCloud Run MCP ServerMCP server to deploy apps to Cloud RunMicrosoft 365 MCP ServerAn MCP server for interacting with Microsoft 365 and Office services through the Graph API.
FMRS47 / 100 · D61 / 100 · C
Reliability6 / 208 / 20
Security and permissions3 / 2013 / 20
Maintenance13 / 2010 / 20
Documentation13 / 2016 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers and teams wanting to integrate deployment into AI workflows
  • Users already using Google Cloud and Cloud Run
  • AI agents that need to quickly prototype or deploy applications
  • 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
  • Deployments requiring local hosting or other cloud provider support
  • Users wanting fine-grained IAM control without skipping permission checks
  • Seeking GitOps or fully automated CI/CD without MCP/CLI
  • 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 Google Cloud IAM credentials to access Cloud Run APIs.
  • Authentication via `gcloud auth login` and `gcloud auth application-default login`.
  • Deployment requires appropriate Cloud Run permissions like `run.services.create` and `run.services.update`.
  • Project creation requires permissions like `resourcemanager.projects.create`.
  • 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
  • Using remote MCP server without authentication may lead to unauthorized access.
  • IAM checks are skipped by default (`SKIP_IAM_CHECK=true`), potentially allowing overly permissive access.
  • Deploying file contents may expose sensitive data if provided in prompts.
  • DNS rebinding risk unless host validation is enabled (`ENABLE_HOST_VALIDATION`).
  • 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 clientsGemini CLI, Claude Desktop, VS Code, Cursor, Windsurf, AntigravityClaude Desktop, Open WebUI
Tools710