What is the key difference between Kage and Moxie Docs MCP?

Kage belongs to the Knowledge & Memory category with local stdio execution, while Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Kage or Moxie Docs MCP 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 Kage and Moxie Docs MCP free or paid?

Kage operates under a Free / Open Source model (No auth required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Kage lists 6 tools with 3 views and 32 GitHub stars. Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both kage-core-kage and moxie-docs-mcp 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, Kage has a Quality Score of 61 /100 ( Good ) with 3 views, 0 installs, and 32 GitHub stars. Moxie Docs MCP holds a Quality Score of 82 /100 ( Excellent ) with 17 views, 25 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Kage vs Moxie Docs MCP

In-depth architectural comparison of the Kage and Moxie Docs MCP 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

Kage

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 82/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Kage if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs MCP 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 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: Git-native memory packets, Open Knowledge Format bundles, Deterministic citation verification.

Explore Kage Details

Choose Moxie Docs MCP 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: MOXIE_TOKEN.
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Feature & Specification Comparison

Specification	Kage kage-core Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	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	MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Tools & Capabilities Breakdown

Kage Tools (6)

Git-native memory packets

Open Knowledge Format bundles

Deterministic citation verification

Stale-memory detection and withholding

Local BM25 and vector search

Agent wiring and MCP configuration

Moxie Docs MCP Tools (12)

moxie.get_ai_context

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

Kage Configuration

mcpServers (Claude Desktop / Cursor)

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

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ],
      "env": {
        "MOXIE_TOKEN": "YOUR_MOXIE_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Kage More alternatives to Moxie Docs MCP Knowledge & Memory category hub