Kirok Memory vs Recall — persistent memory for agents

In-depth architectural comparison of the Kirok Memory and Recall — persistent memory for agents MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Kirok Memory when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Kirok Memory Details

R

Choose Recall — persistent memory for agents when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Recall — persistent memory for agents Details

Feature & Specification Comparison

Specification	Kirok Memory Knowledge & Memory	R Recall — persistent memory for agents Knowledge & Memory
Summary	Persistent memory for AI agents - hybrid semantic + keyword recall with autonomous consolidation	Persistent memory for AI agents: save facts under keys, recall them in later sessions. Free, no LLM.
Category & Scope	Knowledge & Memory	Knowledge & Memory

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "kirok-memory": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

{
  "mcpServers": {
    "recall-persistent-memory-for-agents": {
      "url": "https://recall.notdown-app.workers.dev"
    }
  }
}

Related MCP Server Comparisons