What is the key difference between Mengram and Cognee?

Mengram belongs to the Knowledge & Memory category with local stdio execution, while Cognee belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mengram or Cognee in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Mengram and Cognee free or paid?

Mengram operates under a Freemium model (API Key required). Cognee operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Mengram lists 6 tools with 2 views and 187 GitHub stars. Cognee lists 6 tools with 3 views and 29,870 GitHub stars.

Can I use both Mengram and Cognee together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Mengram or Cognee in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Mengram and Cognee free to use, or do they require API keys?

Mengram is listed under a Freemium model with API Key required . Cognee operates under a BYOK (Pay Provider Direct) model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Mengram and Cognee at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both alibaizhanov-mengram and topoteretes-cognee as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Mengram has a Quality Score of 48 /100 ( Fair ) with 2 views, 0 installs, and 187 GitHub stars. Cognee holds a Quality Score of 48 /100 ( Fair ) with 3 views, 0 installs, and 29,870 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Mengram vs Cognee

In-depth architectural comparison of the Mengram 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.

At a Glance & Executive Verdict

Mengram

Knowledge & Memory · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

Cognee

Knowledge & Memory · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Mengram if you need specialized Knowledge & Memory tools running via a local process. Choose Cognee if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mengram when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: MENGRAM_API_KEY.
Primary tools included: Semantic, episodic, and procedural memory types, Procedures evolve from failure feedback, Native multilingual retrieval (23 languages).

Explore Mengram 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: Supports ingestion from 30+ data sources, Combines vector embeddings with graph-based reasoning, Self-hosted knowledge graph with ontology generation.

Explore Cognee Details

Feature & Specification Comparison

Specification	Mengram alibaizhanov Knowledge & Memory	Cognee topoteretes Knowledge & Memory
Summary	Human-like memory layer for AI agents with semantic, episodic, and procedural memory. Claude Code hooks (auto-save, auto-recall, cognitive profile). 29 MCP tools, knowledge graph, smart triggers, multi-user isolation. Python & JS SDKs.	Memory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal	48/100 (Fair)	48/100 (Fair)
Transport Protocol	Local Subprocess (stdio)	Local Subprocess (stdio)
Auth Requirement	API Key required	API Key required
Pricing Model	Freemium	BYOK (Pay Provider Direct)
Required Env Vars	`MENGRAM_API_KEY`	`LLM_API_KEY`
Compatible Clients	Claude DesktopCursorWindsurfClineVS Code	Claude DesktopCursorWindsurfClineVS Code
Install path signal	`uvx · low`	`npx · low`
Engagement & Health	2 views 0 copies 0 upvotes 187 stars	3 views 0 copies 0 upvotes 29,870 stars
Verified / Official	Community Listing	Community Listing
Open full listing	View Mengram Listing	View Cognee Listing

Tools & Capabilities Breakdown

Mengram Tools (6)

Semantic, episodic, and procedural memory types

Procedures evolve from failure feedback

Native multilingual retrieval (23 languages)

Knowledge graph and smart triggers

Claude Code hooks for auto-save, auto-recall, and session persistence

Multi-user data isolation

Cognee Tools (6)

Supports ingestion from 30+ data sources

Combines vector embeddings with graph-based reasoning

Self-hosted knowledge graph with ontology generation

Persistent memory for AI agents with cross-session recall

User/tenant isolation and audit traceability

OpenTelemetry (OTEL) collector integration

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

Mengram Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "alibaizhanov-mengram": {
      "command": "uvx",
      "args": [
        "alibaizhanov-mengram"
      ],
      "env": {
        "MENGRAM_API_KEY": "YOUR_MENGRAM_API_KEY_HERE"
      }
    }
  }
}

Cognee Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Mengram is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Cognee belongs to Knowledge & Memory using local stdio subprocess. Select Mengram when you need capabilities focused on knowledge & memory and Cognee when you require tools for knowledge & memory.

More alternatives to Mengram More alternatives to Cognee Knowledge & Memory category hub