Google Workspace vs Gmail MCP
A side-by-side look at the Google Workspace and Gmail MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Workspace for communication work as a local process; choose Gmail MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Workspace when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET.
Choose Gmail MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GMAIL_MCP_RECIPIENT_PAIRING.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 51/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET | GMAIL_MCP_RECIPIENT_PAIRING |
| Verified owner | Community listing | Community listing |
| GitHub stars | 192 | 15 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Workspace | View Gmail MCP |
Tools & capabilities
Google Workspace tools
No tool names declared yet. Check the project README from the listing page.
Gmail MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Workspace
{
"mcpServers": {
"google-workspace-2": {
"command": "npx",
"args": [
"-y",
"@aaronsb/google-workspace-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
"GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE"
}
}
}
}
Gmail MCP
{
"mcpServers": {
"klodr-gmail-mcp": {
"command": "npx",
"args": [
"-y",
"@klodr/gmail-mcp"
],
"env": {
"GMAIL_MCP_RECIPIENT_PAIRING": "YOUR_GMAIL_MCP_RECIPIENT_PAIRING_HERE"
}
}
}
}
Frequently asked questions
Google Workspace is categorized under Communication and uses a local stdio subprocess. Gmail MCP belongs to Communication and uses a local stdio subprocess. Pick Google Workspace for communication work and Gmail MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google Workspace has no declared pricing — check the project's own site. Gmail MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-workspace-2 and klodr-gmail-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Workspace has a quality signal of 51/100 (Good) with 1 views, 0 installs and 192 GitHub stars. Gmail MCP has 57/100 (Good) with 3 views, 0 installs and 15 GitHub stars.