Cognitive AI Memory vs Honcho

A side-by-side look at the Cognitive AI Memory and Honcho MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Cognitive AI Memory logoCognitive AI MemoryKnowledge & Memory · Local subprocess (stdio)Ebbinghaus-based persistent memory for Claude. Memories decay with time, strengthen on recall.44FairAuth: not declaredHoncho logoHonchoKnowledge & Memory · Local subprocess (stdio)Memory that reasons: continual learning for stateful agents. Better context, fewer tokens.48FairAuth: not declared

Verdict: choose Cognitive AI Memory for knowledge & memory work as a local process; choose Honcho 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?

Cognitive AI Memory logoChoose Cognitive AI Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
Explore Cognitive AI Memory

Honcho logoChoose Honcho when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: HONCHO_API_KEY, HONCHO_URL.
Explore Honcho

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCognitive AI Memory logoCognitive AI MemoryHoncho logoHoncho
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal44/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedHONCHO_API_KEYHONCHO_URL
Verified ownerCommunity listingCommunity listing
GitHub stars2707,746
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Cognitive AI Memory tools

No tool names declared yet. Check the project README from the listing page.

Honcho 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.

Cognitive AI Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cognitive-ai-memory": {
      "command": "uvx",
      "args": [
        "yourmemory"
      ]
    }
  }
}

Honcho

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "honcho": {
      "command": "uvx",
      "args": [
        "honcho-ai"
      ],
      "env": {
        "HONCHO_API_KEY": "YOUR_HONCHO_API_KEY_HERE",
        "HONCHO_URL": "YOUR_HONCHO_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Cognitive AI Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Honcho belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Cognitive AI Memory for knowledge & memory work and Honcho 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.

Cognitive AI Memory has no declared pricing — check the project's own site. Honcho has no declared pricing — check the project's own site. 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 cognitive-ai-memory and honcho as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Cognitive AI Memory has a quality signal of 44/100 (Fair) with 3 views, 0 installs and 270 GitHub stars. Honcho has 48/100 (Fair) with 1 views, 0 installs and 7,746 GitHub stars.