Mbox MCP vs Agent Comms
A side-by-side look at the Mbox MCP and Agent Comms MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mbox MCP for communication work as a local process; choose Agent Comms 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 Mbox MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You want tools like
open_archive, search_messages, get_message.
Choose Agent Comms when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You want tools like
agent_comms.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 56/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 34 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 1 |
| Full listing | View Mbox MCP | View Agent Comms |
Tools & capabilities
Mbox MCP tools 3
open_archiveIndex an .mbox file or .eml directory: message count, date range, top senderssearch_messagesSearch by keyword, sender, subject, date range — plus bounded body-text searchget_messageFully parse one message: decoded body, headers, attachment names/sizes
Agent Comms tools 1
agent_commsCross-harness agent communication mesh. Actions: register, update, whoami, web_url, create_room, list_rooms, join_room, leave_room, send, dm, list_agents, read_room, invite, decline_invite, kick, destroy_room. Pending incoming messages are included in every response.
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.
Mbox MCP
{
"mcpServers": {
"mbox-mcp": {
"command": "npx",
"args": [
"-y",
"mbox-mcp"
]
}
}
}
Agent Comms
{
"mcpServers": {
"agent-comms": {
"command": "npx",
"args": [
"-y",
"agent-comms"
]
}
}
}
Frequently asked questions
Mbox MCP is categorized under Communication and uses a local stdio subprocess. Agent Comms belongs to Communication and uses a local stdio subprocess. Pick Mbox MCP for communication work and Agent Comms 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.
Mbox MCP has no declared pricing — check the project's own site. Agent Comms 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 mbox-mcp and agent-comms as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mbox MCP has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Agent Comms has 64/100 (Good) with 1 views, 0 installs and 34 GitHub stars.