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 CalendarNextcloud MCP ServerA production-ready MCP server that connects AI assistants to your Nextcloud instance.
FMRS61 / 100 · C67 / 100 · C
Reliability8 / 2010 / 20
Security and permissions13 / 2012 / 20
Maintenance13 / 2016 / 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
  • Users who want to integrate AI assistants (like Claude Desktop or IDEs) with a self-hosted Nextcloud instance.
  • Developers and power users who need deep CRUD operations across multiple Nextcloud apps.
  • Teams that prefer Docker or Kubernetes deployment.
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 who don't want to self-host (consider managed service Astrolabe Cloud).
  • Users who need only simple read-only access (this server is more comprehensive).
  • Users who require official support (it is not an official Nextcloud project).
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 a Nextcloud username and app password (or OAuth).
  • Read/write access to the selected Nextcloud apps (Notes, Calendar, Contacts, Files, etc.).
  • For semantic search, needs external services: Qdrant and Ollama (disabled by default).
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
  • Credential storage with app passwords may pose a security risk if exposed.
  • The server can access a user's full Nextcloud data, so proper access controls are necessary.
  • Experimental semantic search relies on external services, which may introduce security and privacy issues.
  • Tag-based exclusion (EXCLUDED_TAGS) depends on system tags to hide sensitive files, misconfiguration could expose data.
Supported clientsClaude Desktop, Gemini CLI, claude.ai custom connectorsClaude Desktop
Tools113