Penfield MCP vs Swarmmesh
A side-by-side look at the Penfield MCP and Swarmmesh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Penfield MCP for knowledge & memory work as a local process; choose Swarmmesh for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Penfield MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Choose Swarmmesh when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 49/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Penfield MCP | View Swarmmesh |
Tools & capabilities
Penfield MCP tools
No tool names declared yet. Check the project README from the listing page.
Swarmmesh 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.
Penfield MCP
{
"mcpServers": {
"penfieldlabs-penfield-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
Swarmmesh
{
"mcpServers": {
"swarmmesh": {
"command": "uvx",
"args": [
"swarmmesh-cli"
]
}
}
}
Frequently asked questions
Penfield MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Swarmmesh belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Penfield MCP for knowledge & memory work and Swarmmesh for knowledge & memory.
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.
Penfield MCP is listed as free. Auth: oauth 2.0. Swarmmesh is listed as free. Auth: no auth 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 penfieldlabs-penfield-mcp and swarmmesh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Penfield MCP has a quality signal of 49/100 (Fair) with 4 views, 0 installs and 6 GitHub stars. Swarmmesh has 41/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.