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