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.

DimensionRaindrop MCP ServerConnect Raindrop.io to your AI assistant with natural languageMicrosoft 365 MCP ServerAn MCP server for interacting with Microsoft 365 and Office services through the Graph API.
FMRS52 / 100 · D61 / 100 · C
Reliability8 / 208 / 20
Security and permissions10 / 2013 / 20
Maintenance12 / 2010 / 20
Documentation12 / 2016 / 20
Setup experience10 / 2014 / 20
Best for
  • Individuals and teams who rely on Raindrop.io for bookmark management.
  • Users who want to control their bookmarks via an AI assistant using natural language.
  • 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 without a Raindrop.io account or who cannot provide an API token.
  • Users who require an official hosted solution (the official Streamable HTTP endpoint exists, but this server is self-hosted).
  • 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 a Raindrop.io API token, which grants read and write access to the user's collections, bookmarks, tags, highlights, and trash.
  • 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
  • Requires managing an API token; leakage may lead to unauthorized modifications of bookmark data.
  • Some destructive tools (e.g., empty_trash, remove_duplicates) require confirmation but are irreversible.
  • Community-maintained, may be less stable than official servers.
  • 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, Gemini CLI, Codex, Claude Code, GitHub CopilotClaude Desktop, Open WebUI
Tools1710