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.

DimensionEdgeOne Makers MCP ServerMCP service for deploying HTML content to EdgeOne Makers and getting a public URLMicrosoft 365 MCP ServerAn MCP server for interacting with Microsoft 365 and Office services through the Graph API.
FMRS35 / 100 · D61 / 100 · C
Reliability6 / 208 / 20
Security and permissions6 / 2013 / 20
Maintenance8 / 2010 / 20
Documentation8 / 2016 / 20
Setup experience7 / 2014 / 20
Best for
  • Developers who need to quickly deploy HTML content to EdgeOne Makers and get a public URL
  • Users who want to integrate deployment into their MCP-driven workflows
  • 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
  • Users who do not need EdgeOne Makers deployment
  • Users who cannot use Node.js environment
  • 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
  • API token (optional) to skip login
  • Project name (optional) to select project
  • Browser login (optional)
  • 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
  • API token leakage could lead to unauthorized deployments
  • Deployed content may be publicly accessible, so avoid exposing sensitive information
  • 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, Open WebUI
Tools010