Krusch Context MCP vs Memento MCP
A side-by-side look at the Krusch Context MCP and Memento MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
Krusch Context MCPKnowledge & Memory · Local subprocess (stdio)Persistent working memory and invariant steering MCP server for AI coding agents (Claude Code, Cursor, Windsurf). Captures architectural decisions, enforces project rules with pre-commit audits, and supersedes obsolete facts with temporal lineage. SQLite-first, zero Docker, <350 tokens60GoodAuth: no auth requiredVerdict: choose Krusch Context MCP for knowledge & memory work as a local process; choose Memento MCP for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
KChoose Krusch Context MCP 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.
Choose Memento MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Krusch Context MCP | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 60/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 71 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Krusch Context MCP | View Memento MCP |
Tools & capabilities
Krusch Context MCP tools
No tool names declared yet. Check the project README from the listing page.
Memento MCP 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.
Krusch Context MCP
{
"mcpServers": {
"krusch-context-mcp": {
"command": "npx",
"args": [
"-y",
"krusch-context-mcp"
]
}
}
}
Memento MCP
No confirmed install command for Memento MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Krusch Context MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Memento MCP belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Krusch Context MCP for knowledge & memory work and Memento MCP 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. Memento MCP has no confirmed install command yet — follow its own setup instructions.
Krusch Context MCP is listed as free. Auth: no auth required. Memento MCP 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 krusch-context-mcp and lfrmonteiro99-memento-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Krusch Context MCP has a quality signal of 60/100 (Good) with 1 views, 0 installs and 71 GitHub stars. Memento MCP has 43/100 (Fair) with 2 views, 0 installs and 2 GitHub stars.