Basic Memory vs Swarmmesh
A side-by-side look at the Basic Memory 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 Basic Memory 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 Basic Memory 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.
- You want tools like
write_note, read_note, edit_note.
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 | 64/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,289 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 21 | Not listed |
| Full listing | View Basic Memory | View Swarmmesh |
Tools & capabilities
Basic Memory tools 21
write_noteread_noteedit_notemove_notedelete_noteread_contentview_notesearch_notesrecent_activitylist_directorybuild_contextlist_memory_projects- +9 more on 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.
Basic Memory
{
"mcpServers": {
"basicmachines-co-basic-memory": {
"command": "uvx",
"args": [
"--prerelease=allow",
"basic-memory"
]
}
}
}
Swarmmesh
{
"mcpServers": {
"swarmmesh": {
"command": "uvx",
"args": [
"swarmmesh-cli"
]
}
}
}
Frequently asked questions
Basic Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Swarmmesh belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Basic Memory 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.
Basic Memory is listed as freemium — a free tier with paid plans. Auth: no auth required. 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 basicmachines-co-basic-memory and swarmmesh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Basic Memory has a quality signal of 64/100 (Good) with 2 views, 0 installs and 4,289 GitHub stars. Swarmmesh has 41/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.