← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionMicrosoft 365 MCP ServerAn MCP server for interacting with Microsoft 365 and Office services through the Graph API.reMarkable MCP ServerUse your reMarkable tablet as a second brain for AI assistants. Read documents, browse files, extract text, and OCR handwriting.
FMRS61 / 100 · C65 / 100 · C
Reliability8 / 2010 / 20
Security and permissions13 / 2012 / 20
Maintenance10 / 2014 / 20
Documentation16 / 2016 / 20
Setup experience14 / 2013 / 20
Best for
  • 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.
  • reMarkable users who want to leverage their device's notes and documents in AI workflows.
  • Remote or headless setups where device-free access is needed (cloud mode).
  • Users who prefer fast offline access over USB without subscription (USB Web mode).
Not for
  • 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).
  • Users without a reMarkable device or who are unwilling to manage multiple API keys.
  • Teams needing official support or enterprise SLA.
  • Users who want to customize the protocol without owning the hardware.
Required permissions
  • 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.
  • Requires authentication token for reMarkable Cloud API (`REMARKABLE_TOKEN`) — keep it secret.
  • USB/SSH modes require USB connection and/or SSH access to the tablet filesystem.
  • Write operations are enabled by default; destructive deletes require confirmation (if client supports elicitation) or setting `REMARKABLE_SKIP_CONFIRM=1`.
  • Optional Google Vision API key for OCR.
Risks and side effects
  • 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.
  • Write tools can lead to data loss; deletes are destructive and should be used with caution.
  • Cloud mode requires a reMarkable Connect subscription, which may incur costs.
  • Google Vision OCR may incur costs (1000 free requests/month, then ~$1.50 per 1000).
  • Potential exposure of sensitive notes to AI providers if not properly managed.
  • SSH mode requires developer mode, which may void warranty.
Supported clientsClaude Desktop, Open WebUIClaude, VS Code, ChatGPT
Tools1013