Deliveriq MCP vs Groundmail
A side-by-side look at the Deliveriq MCP and Groundmail MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Deliveriq MCP for communication work as a local process; choose Groundmail for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Deliveriq 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:
DELIVERIQ_API_KEY.
Choose Groundmail when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
GROUNDMAIL_API_KEY, GROUNDMAIL_API_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 41/100 · Fair | 58/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | DELIVERIQ_API_KEY | GROUNDMAIL_API_KEYGROUNDMAIL_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Deliveriq MCP | View Groundmail |
Tools & capabilities
Deliveriq MCP tools
No tool names declared yet. Check the project README from the listing page.
Groundmail 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.
Deliveriq MCP
{
"mcpServers": {
"deliveriq-mcp": {
"command": "npx",
"args": [
"-y",
"@deliveriq/mcp"
],
"env": {
"DELIVERIQ_API_KEY": "YOUR_DELIVERIQ_API_KEY_HERE"
}
}
}
}
Groundmail
{
"mcpServers": {
"groundmail": {
"command": "npx",
"args": [
"-y",
"groundmail-mcp"
],
"env": {
"GROUNDMAIL_API_KEY": "YOUR_GROUNDMAIL_API_KEY_HERE",
"GROUNDMAIL_API_URL": "YOUR_GROUNDMAIL_API_URL_HERE"
}
}
}
}
Frequently asked questions
Deliveriq MCP is categorized under Communication and uses a local stdio subprocess. Groundmail belongs to Communication and uses a remote HTTP/SSE transport. Pick Deliveriq MCP for communication work and Groundmail 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.
Deliveriq MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Groundmail has no declared pricing — check the project's own site. 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 deliveriq-mcp and groundmail as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Deliveriq MCP has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. Groundmail has 58/100 (Good) with 0 views, 0 installs and 0 GitHub stars.