Rag Kb vs Krimto
A side-by-side look at the Rag Kb and Krimto MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Rag Kb for knowledge & memory work over a hosted endpoint; choose Krimto 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 Rag Kb when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
Choose Krimto 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 | 51/100 · Good | 53/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 | 3 | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Rag Kb | View Krimto |
Tools & capabilities
Rag Kb tools
No tool names declared yet. Check the project README from the listing page.
Krimto 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.
Rag Kb
{
"mcpServers": {
"fish827-08-rag-kb": {
"url": "https://api.deepseek.com"
}
}
}
Krimto
{
"mcpServers": {
"krimto-labs-krimto": {
"command": "npx",
"args": [
"-y",
"@krimto-labs/krimto"
]
}
}
}
Frequently asked questions
Rag Kb is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Krimto belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Rag Kb for knowledge & memory work and Krimto 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.
Rag Kb has no declared pricing — check the project's own site. Krimto 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 fish827-08-rag-kb and krimto-labs-krimto as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Rag Kb has a quality signal of 51/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Krimto has 53/100 (Good) with 5 views, 0 installs and 7 GitHub stars.