Agentkits Memory vs Krusch Context MCP
A side-by-side look at the Agentkits Memory 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 Agentkits Memory for knowledge & memory work as a local process; 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 Agentkits 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.
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 | 51/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 3 | 71 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Agentkits Memory | View Krusch Context MCP |
Tools & capabilities
Agentkits Memory tools
No tool names declared yet. Check the project README from 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.
Agentkits Memory
{
"mcpServers": {
"aitytech-agentkits-memory": {
"command": "npx",
"args": [
"-y",
"@aitytech/agentkits-memory"
]
}
}
}
Krusch Context MCP
{
"mcpServers": {
"krusch-context-mcp": {
"command": "npx",
"args": [
"-y",
"krusch-context-mcp"
]
}
}
}
Frequently asked questions
Agentkits Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Krusch Context MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agentkits Memory 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.
Agentkits Memory is listed as free. Auth: no auth required. 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 aitytech-agentkits-memory and krusch-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentkits Memory has a quality signal of 51/100 (Good) with 5 views, 0 installs and 3 GitHub stars. Krusch Context MCP has 60/100 (Good) with 1 views, 0 installs and 71 GitHub stars.