What is the key difference between Cortex and Kg?

Cortex belongs to the Knowledge & Memory category with local stdio execution, while Kg belongs to the Knowledge & Memory category with local stdio execution.

How do I install Cortex or Kg 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 Cortex and Kg free or paid?

Cortex operates under a Free / Open Source model (No auth required). Kg operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cortex lists 0 tools with 0 views and 1 GitHub stars. Kg lists 0 tools with 0 views and 9 GitHub stars.

Can I use both Cortex and Kg 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.

Side-by-Side Model Context Protocol Comparison

Cortex vs Kg

In-depth architectural comparison of the Cortex and Kg 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

Cortex

Knowledge & Memory · Local stdio

Quality: 36/100 (Fair) | Auth: No auth required

Knowledge & Memory · Local stdio

Quality: 31/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Cortex if you need specialized Knowledge & Memory tools running via a local process. Choose Kg 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 Cortex 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).

Explore Cortex Details

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

Explore Kg Details

Feature & Specification Comparison

Specification	Cortex Knowledge & Memory	Kg Knowledge & Memory
Summary	Local multi-client RAG server over the Model Context Protocol.	Local knowledge graph memory MCP server for AI assistants.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Cortex Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Kg Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Cortex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cortex-3": {
      "command": "npx",
      "args": [
        "-y",
        "cortex-3"
      ]
    }
  }
}

Kg Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kg": {
      "command": "npx",
      "args": [
        "-y",
        "kg"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Cortex More alternatives to Kg Knowledge & Memory category hub