Sentfromai MCP vs Shipmail MCP
A side-by-side look at the Sentfromai MCP and Shipmail MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sentfromai MCP for communication work as a local process; choose Shipmail 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 Sentfromai MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SENTFROMAI_API_KEY, SENTFROMAI_BASE_URL.
Choose Shipmail 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 44/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | SENTFROMAI_API_KEYSENTFROMAI_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Sentfromai MCP | View Shipmail MCP |
Tools & capabilities
Sentfromai MCP tools
No tool names declared yet. Check the project README from the listing page.
Shipmail 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.
Sentfromai MCP
{
"mcpServers": {
"mcp-26": {
"command": "npx",
"args": [
"-y",
"sentfromai-mcp"
],
"env": {
"SENTFROMAI_API_KEY": "YOUR_SENTFROMAI_API_KEY_HERE",
"SENTFROMAI_BASE_URL": "YOUR_SENTFROMAI_BASE_URL_HERE"
}
}
}
}
Shipmail MCP
{
"mcpServers": {
"jcoulaud-shipmail-mcp": {
"command": "npx",
"args": [
"-y",
"shipmail-mcp"
]
}
}
}
Frequently asked questions
Sentfromai MCP is categorized under Communication and uses a local stdio subprocess. Shipmail MCP belongs to Communication and uses a local stdio subprocess. Pick Sentfromai MCP for communication work and Shipmail 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.
Sentfromai MCP has no declared pricing — check the project's own site. Shipmail MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 mcp-26 and jcoulaud-shipmail-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sentfromai MCP has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Shipmail MCP has 55/100 (Good) with 2 views, 0 installs and 1 GitHub stars.