What is the key difference between Memory and Cortex?

Memory belongs to the Knowledge & Memory category with local stdio execution, while Cortex belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

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

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

Which MCP server has more tools and community activity?

Memory lists 0 tools with 0 views and 0 GitHub stars. Cortex lists 0 tools with 0 views and 0 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both memory-2 and cortex-2 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, Memory has a Quality Score of 29 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Cortex holds a Quality Score of 45 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Memory vs Cortex

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

Memory

Knowledge & Memory · Local stdio

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

Cortex

Knowledge & Memory · Remote HTTP/SSE

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

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

Which MCP Server Should You Choose?

Choose Memory 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 Memory Details

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

Explore Cortex Details

Feature & Specification Comparison

Specification	M Memory Knowledge & Memory	C Cortex Knowledge & Memory
Summary	Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.	Shared, persistent semantic memory for your AI: save, search by meaning, recall with sources.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Memory Tools (0)

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

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

Memory Configuration

mcpServers (Claude Desktop / Cursor)

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

Cortex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cortex-2": {
      "url": "https://skynetlab-cortex.com"
    }
  }
}

Frequently Asked Questions

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

More alternatives to Memory More alternatives to Cortex Knowledge & Memory category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with Memory

Popular comparisons with Cortex

Cortex vs Moxie Docs MCP