Google Drive MCP Server vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Google Drive MCP Server MCP Servers	MCP Everything Server MCP Servers
Tagline	Read, list, and search your Google Drive from any MCP-compatible AI client.	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open-source (MIT). Google Cloud/Drive API usage governed by Google's free quotas.	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model	—	—
Editorial score	—	—
Use cases	Ground Claude in a folder of meeting notesPull the latest spec doc into a coding agentSummarise a Google Sheet without downloadingSearch Drive from Claude DesktopFetch Docs as Markdown into a RAG pipelineMulti-server MCP setup with GitHub and SlackExtract Slides content as plain text for briefingsReference implementation for a custom Drive MCP fork	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros	Official reference implementation - clean, minimal code that's easy to audit or fork. Auto-converts Google Docs, Sheets, Slides, and Drawings to LLM-friendly formats out of the box. Works with any MCP client (Claude Desktop, Cursor, VS Code, Continue, custom agents). Three install paths: npx, Docker, and one-click VS Code - no build step required for most users. MIT-licensed and open source, so you can fork and extend it freely. Standard OAuth 2.0 with local credential storage - no third-party broker in the loop.	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons	Archived on 29 May 2025 - no upstream maintenance, security fixes, or new features from Anthropic. Read-only: no create, edit, move, share, or delete operations on Drive files. OAuth setup is fiddly - you have to stand up a Google Cloud project and consent screen yourself. Search returns only names and MIME types, not snippets or ranked relevance. No native folder-scoping, permission filtering, or workspace-account controls beyond what the OAuth token grants.	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Website	github.com	github.com

Pick Google Drive MCP Server if

✅ Official reference implementation - clean, minimal code that's easy to audit or fork.
✅ Auto-converts Google Docs, Sheets, Slides, and Drawings to LLM-friendly formats out of the box.
✅ Works with any MCP client (Claude Desktop, Cursor, VS Code, Continue, custom agents).
✅ Three install paths: npx, Docker, and one-click VS Code - no build step required for most users.

Pick MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →