Honcho vs Cognee

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

Honcho logoHonchoKnowledge & Memory · Local subprocess (stdio)Memory that reasons: continual learning for stateful agents. Better context, fewer tokens.48FairAuth: not declaredCognee logoCogneeKnowledge & MemoryMemory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources48FairAuth: no auth required

Verdict: choose Honcho for knowledge & memory work as a local process; choose Cognee for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

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

Cognee logoChoose Cognee when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: LLM_API_KEY.
Explore Cognee

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHoncho logoHonchoCognee logoCognee
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal48/100 · Fair48/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsHONCHO_API_KEYHONCHO_URLLLM_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars7,70032,581
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Honcho tools

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

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

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"
      }
    }
  }
}

Cognee

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

Frequently asked questions

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

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

On AllMCPs, Honcho has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 7,700 GitHub stars. Cognee has 48/100 (Fair) with 5 views, 0 installs and 32,581 GitHub stars.