Continuum vs Krusch Context MCP
A side-by-side look at the Continuum and Krusch Context 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 Continuum for knowledge & memory work over a hosted endpoint; choose Krusch Context MCP 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 Continuum when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
project_list, project_get, project_create.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Krusch Context MCP | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 53/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 98 | 71 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | Not listed |
| Full listing | View Continuum | View Krusch Context MCP |
Tools & capabilities
Continuum tools 17
project_listEnumerate registered projectsproject_getFetch one projectproject_createRegister project, seed PLOT.md + knowledgeproject_renameRename a projectproject_deleteCascade delete (project + agents + lessons)plotRead PLOT.mdplot_updateApply a unified git-format diff (zero fuzz, exact context match)knowledge_listLesson metadata (slug, kind, agentSlug, timestamps). Optional `kind` filter. **No content.knowledge_searchSemantic query → ranked metadata. `q` free-text intent, optional `kind`, optional `limit`. **No content.knowledge_getRead one lesson by slug — full bodyknowledge_createRecord a new lesson — `kind: 'fundamental' \knowledge_updateReplace lesson content. Re-embeds on save.- +5 more on the listing page
Krusch Context 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.
Continuum
{
"mcpServers": {
"continuum-2": {
"url": "http://127.0.0.1:7776/mcp"
}
}
}
Krusch Context MCP
{
"mcpServers": {
"krusch-context-mcp": {
"command": "npx",
"args": [
"-y",
"krusch-context-mcp"
]
}
}
}
Frequently asked questions
Continuum is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Krusch Context MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Continuum for knowledge & memory work and Krusch Context 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.
Continuum has no declared pricing — check the project's own site. Krusch Context 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 continuum-2 and krusch-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Continuum has a quality signal of 53/100 (Good) with 1 views, 0 installs and 98 GitHub stars. Krusch Context MCP has 60/100 (Good) with 1 views, 0 installs and 71 GitHub stars.