Google Drive MCP Server vs Slack MCP Server

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

	Google Drive MCP Server MCP Servers	Slack MCP Server MCP Servers
Tagline	Read, list, and search your Google Drive from any MCP-compatible AI client.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
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 / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
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	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
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.	Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
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.	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
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 Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →