Gmail MCP vs Nestr MCP
A side-by-side look at the Gmail MCP and Nestr MCP 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 Nestr 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 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 Nestr MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
NESTR_API_KEY, NESTR_OAUTH_TOKEN. - You want tools like
nestr_list_workspaces, nestr_get_workspace, nestr_create_workspace.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 57/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Free | Not declared |
| Required env vars | GMAIL_MCP_RECIPIENT_PAIRING | NESTR_API_KEYNESTR_OAUTH_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16 | 6 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 69 |
| Full listing | View Gmail MCP | View Nestr MCP |
Tools & capabilities
Gmail MCP tools
No tool names declared yet. Check the project README from the listing page.
Nestr MCP tools 69
nestr_list_workspacesList accessible workspacesnestr_get_workspaceGet workspace detailsnestr_create_workspaceCreate a new workspace (OAuth only)nestr_searchSearch for nests (tasks, projects, roles)nestr_get_meGet current user identity and workspace listnestr_get_nestGet details of a specific nest (supports batch fetch with comma-separated IDs; single-nest `provenance`/`rights`/`whoCan` flags available)nestr_explain_nestDiagnose one nest: field/property provenance (which label/circle defines each), the caller's composed rights with a deny trace, and (with `whoCan`) who can act on it and who to contactnestr_get_nest_childrenGet child nestsnestr_create_nestCreate a new nestnestr_update_nestUpdate nest propertiesnestr_delete_nestDelete a nestnestr_reorder_nestReorder a nest relative to another- +57 more on 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"
}
}
}
}
Nestr MCP
{
"mcpServers": {
"mcp-348": {
"command": "npx",
"args": [
"-y",
"@nestr/mcp"
],
"env": {
"NESTR_API_KEY": "YOUR_NESTR_API_KEY_HERE",
"NESTR_OAUTH_TOKEN": "YOUR_NESTR_OAUTH_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Gmail MCP is categorized under Communication and uses a local stdio subprocess. Nestr MCP belongs to Communication and uses a local stdio subprocess. Pick Gmail MCP for communication work and Nestr 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.
Gmail MCP is listed as free. Auth: oauth 2.0. Nestr MCP has no declared pricing — check the project's own site. Auth: api key required. 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 mcp-348 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 16 GitHub stars. Nestr MCP has 60/100 (Good) with 0 views, 0 installs and 6 GitHub stars.