Anamnese vs Honcho

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

A
AnamneseKnowledge & Memory
A self-improving memory layer. Your memory, notes, tasks and goals, remembered everywhere.37FairAuth: not declared
Honcho logoHonchoKnowledge & Memory · Local subprocess (stdio)Memory that reasons: continual learning for stateful agents. Better context, fewer tokens.48FairAuth: not declared

Verdict: choose Anamnese for knowledge & memory work; 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?

A
Choose Anamnese when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore Anamnese

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.

Spec
A
Anamnese
Honcho logoHoncho
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/100 · Fair48/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedHONCHO_API_KEYHONCHO_URL
Verified ownerCommunity listingCommunity listing
GitHub stars—7,734
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

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

Anamnese

No confirmed install command for Anamnese yet — follow the setup steps linked from its listing page rather than a guessed package name.

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

Anamnese is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Honcho belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Anamnese 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. Anamnese has no confirmed install command yet — follow its own setup instructions.

Anamnese 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 anamnese and honcho as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Anamnese has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Honcho has 48/100 (Fair) with 1 views, 0 installs and 7,734 GitHub stars.