What is the key difference between Mcp Memory Gateway and Kage?

Mcp Memory Gateway belongs to the Knowledge & Memory category with local stdio execution, while Kage belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mcp Memory Gateway or Kage 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 Mcp Memory Gateway and Kage free or paid?

Mcp Memory Gateway operates under a Free / Open Source model (No auth required). Kage operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mcp Memory Gateway lists 6 tools with 0 views and 25 GitHub stars. Kage lists 6 tools with 0 views and 32 GitHub stars.

Can I use both Mcp Memory Gateway and Kage 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 Mcp Memory Gateway or Kage 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 Mcp Memory Gateway and Kage free to use, or do they require API keys?

Mcp Memory Gateway is listed under a Free / Open Source model with No auth required . Kage operates under a Free / Open Source model with No auth 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 Mcp Memory Gateway and Kage at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both igorganapolsky-mcp-memory-gateway and kage-core-kage 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, Mcp Memory Gateway has a Quality Score of 52 /100 ( Good ) with 0 views, 0 installs, and 25 GitHub stars. Kage holds a Quality Score of 55 /100 ( Good ) with 0 views, 0 installs, and 32 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Mcp Memory Gateway vs Kage

In-depth architectural comparison of the Mcp Memory Gateway and Kage 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

Mcp Memory Gateway

Knowledge & Memory · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Kage

Knowledge & Memory · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Verdict Summary: Choose Mcp Memory Gateway if you need specialized Knowledge & Memory tools running via a local process. Choose Kage 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 Mcp Memory Gateway when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: PreToolUse hook enforcement for AI agent tool calls, Local feedback capture and lesson storage, Auto-promotion of repeated failures into blocking rules.

Explore Mcp Memory Gateway Details

Choose Kage when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Memory stored as plain JSON in git following Open Knowledge Format, Deterministic verification rejecting stale or hallucinated citations, Local-only operation with no account or API key required.

Feature & Specification Comparison

Specification	Mcp Memory Gateway IgorGanapolsky Knowledge & Memory	Kage kage-core Knowledge & Memory
Summary	Pre-action gates that prevent AI coding agents from repeating known mistakes. Captures explicit feedback, auto-promotes failures into prevention rules, and enforces them via hooks.	Verified, git-native memory for coding agents. Memory is plain JSON packets committed in your repo, each checked against the code it cites — hallucinated citations rejected at write, stale or changed memory withheld at recall, plus diff-time stale-catch. Local-only (BM25 + vectors), no account, no API key. npx -y @kage-core/kage-graph-mcp install
Category & Scope

Tools & Capabilities Breakdown

Mcp Memory Gateway Tools (6)

PreToolUse hook enforcement for AI agent tool calls

Local feedback capture and lesson storage

Auto-promotion of repeated failures into blocking rules

Configurable strict enforcement mode for deny decisions

Compatibility with Claude Code, Cursor, Codex, Gemini, Amp, Cline, OpenCode

No remote server required on enforcement path

Kage Tools (6)

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

Mcp Memory Gateway Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "igorganapolsky-mcp-memory-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "thumbgate"
      ]
    }
  }
}

Kage Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kage-core-kage": {
      "command": "npx",
      "args": [
        "-y",
        "@kage-core/kage-graph-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Mcp Memory Gateway More alternatives to Kage Knowledge & Memory category hub