Gmail MCP vs PipesHub
A side-by-side look at the Gmail MCP and PipesHub MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gmail MCP for communication work as a local process; choose PipesHub 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 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.
Choose PipesHub when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 57/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | GMAIL_MCP_RECIPIENT_PAIRING | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 15 | 7 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gmail MCP | View PipesHub |
Tools & capabilities
Gmail MCP tools
No tool names declared yet. Check the project README from the listing page.
PipesHub 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.
Gmail MCP
{
"mcpServers": {
"klodr-gmail-mcp": {
"command": "npx",
"args": [
"-y",
"@klodr/gmail-mcp"
],
"env": {
"GMAIL_MCP_RECIPIENT_PAIRING": "YOUR_GMAIL_MCP_RECIPIENT_PAIRING_HERE"
}
}
}
}
PipesHub
{
"mcpServers": {
"pipeshub": {
"command": "npx",
"args": [
"-y",
"@pipeshub-ai/mcp"
]
}
}
}
Frequently asked questions
Gmail MCP is categorized under Communication and uses a local stdio subprocess. PipesHub belongs to Communication and uses a local stdio subprocess. Pick Gmail MCP for communication work and PipesHub 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.
Gmail MCP is listed as free. Auth: oauth 2.0. PipesHub has no declared pricing — check the project's own site. 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 klodr-gmail-mcp and pipeshub as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gmail MCP has a quality signal of 57/100 (Good) with 3 views, 0 installs and 15 GitHub stars. PipesHub has 48/100 (Fair) with 2 views, 0 installs and 7 GitHub stars.