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.

DimensionGoogle Drive MCPSecure MCP access to Google Drive, Docs, Sheets, Slides, and CalendarreMarkable 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
Maintenance13 / 2014 / 20
Documentation15 / 2016 / 20
Setup experience12 / 2013 / 20
Best for
  • Individuals who want to manage Google Drive files from Claude Desktop or another local MCP client
  • Teams or developers who want to self-host and retain control of their own Google credentials and tokens
  • Multi-step Workspace automation spanning Docs, Sheets, Slides, and Calendar
  • 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
  • Users who need an official Google-maintained MCP integration (this is a third-party project)
  • Users who want zero-setup access without creating their own Google Cloud OAuth credentials
  • Use cases needing coverage of the full Google Workspace API surface beyond Drive, Docs, Sheets, Slides, and Calendar
  • 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
  • Google OAuth 2.0 credentials (GOOGLE_DRIVE_OAUTH_CREDENTIALS, required and marked secret)
  • API access scopes for Google Drive, Docs, Sheets, Slides, and Calendar (enabled and authorized by the user in a Google Cloud project)
  • Locally stored OAuth token file (tokens.json), plus member refresh tokens in team-store.json under team mode
  • 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
  • Exposure of tokens.json or team-store.json could allow access to the associated Google account(s); both must be kept secret
  • Running the HTTP transport without binding to 127.0.0.1 or without TLS and access control could allow unauthorized access
  • Granting broader OAuth scopes than the tools actually used can expose more data than necessary
  • 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, Gemini CLI, claude.ai custom connectorsClaude, VS Code, ChatGPT
Tools113