Toffu vs Cognee

In-depth architectural comparison of the Toffu and Cognee 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 Toffu 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).
• Primary tools included: send_message, query_campaign_performance, creative_report.

Explore Toffu Details

Choose Cognee when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: LLM_API_KEY.
• Primary tools included: Persistent and session-scoped memory, Graph, vector, and code-aware retrieval, Text and code ingestion.

Explore Cognee Details

Feature & Specification Comparison

Specification	Toffu Knowledge & Memory	Cognee topoteretes Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

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": {
    "toffu": {
      "url": "https://mcp.toffu.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "topoteretes-cognee": {
      "command": "uvx",
      "args": [
        "cognee"
      ],
      "env": {
        "LLM_API_KEY": "YOUR_LLM_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons