In-depth architectural comparison of the Google MCP and Google Workspace MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Google MCP
Workplace & Productivity · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Google Workspace MCP
Workplace & Productivity · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Google MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Google Workspace MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Google MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: OAuth token management with automatic refresh and re-authentication, Send emails with multi-recipient support and attachments from multiple sources, Cross-platform email attachment download with filename sanitization.
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_REDIRECT_URI, WORKSPACE_MCP_LOG_LEVEL, WORKSPACE_MCP_PORT, WORKSPACE_MCP_HOST.
Collection of Google-native tools (Gmail, Calendar, Drive, Tasks) for MCP with OAuth management, automated token refresh, and auto re-authentication capabilities.
Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.
Category & Scope
Tools & Capabilities Breakdown
Google MCP Tools (6)
OAuth token management with automatic refresh and re-authentication
Send emails with multi-recipient support and attachments from multiple sources
Cross-platform email attachment download with filename sanitization
Calendar event creation, listing, updating, and free slot finding
Drive file operations including search, read, create, update, delete, and sharing
Task list and task management with filtering and status updates
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Google MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Google Workspace MCP belongs to Workplace & Productivity using local stdio subprocess. Select Google MCP when you need capabilities focused on workplace & productivity and Google Workspace MCP when you require tools for workplace & productivity.
Primary tools included: Full coverage of 12 major Google Workspace services with 120+ tools, OAuth 2.1 multi-user authentication with external auth passthrough support, Supports stdio, streamable HTTP, and SSE transports.