Cogvault vs Recallnest
A side-by-side look at the Cogvault and Recallnest MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
CogvaultKnowledge & Memory · Local subprocess (stdio)Local hybrid-search memory for AI agents over plain Markdown. Multi-tenant, offline, no LLM.40FairAuth: not declaredVerdict: choose Cogvault for knowledge & memory work as a local process; choose Recallnest 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?
CChoose Cogvault when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose Recallnest when
- You need dedicated capabilities in the Knowledge & Memory 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 | C Cogvault | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 40/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 15 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Cogvault | View Recallnest |
Tools & capabilities
Cogvault tools
No tool names declared yet. Check the project README from the listing page.
Recallnest 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.
Cogvault
{
"mcpServers": {
"cogvault": {
"command": "uvx",
"args": [
"cogvault"
]
}
}
}
Recallnest
{
"mcpServers": {
"aliceljy-recallnest": {
"command": "npx",
"args": [
"-y",
"recallnest"
]
}
}
}
Frequently asked questions
Cogvault is categorized under Knowledge & Memory and uses a local stdio subprocess. Recallnest belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Cogvault for knowledge & memory work and Recallnest 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.
Cogvault has no declared pricing — check the project's own site. Recallnest is listed as free. 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 cogvault and aliceljy-recallnest as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cogvault has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Recallnest has 59/100 (Good) with 2 views, 0 installs and 15 GitHub stars.