What is the key difference between Memocall and Cortex Plugin?

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

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

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

Which MCP server has more tools and community activity?

Memocall lists 6 tools with 2 views and 2 GitHub stars. Cortex Plugin lists 6 tools with 1 views and 31 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both baodq06-memocall and tt-wang-cortex-plugin 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, Memocall has a Quality Score of 44 /100 ( Fair ) with 2 views, 0 installs, and 2 GitHub stars. Cortex Plugin holds a Quality Score of 55 /100 ( Good ) with 1 views, 0 installs, and 31 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Memocall vs Cortex Plugin

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

Memocall

Knowledge & Memory · Local stdio

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

Cortex Plugin

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Memocall if you need specialized Knowledge & Memory tools running via a local process. Choose Cortex Plugin 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 Memocall 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: Reads local ~/.claude/projects transcript files only, Returns compact Markdown with tool call outputs elided, Supports session listing, searching, loading, outlining, and in-session search.

Explore Memocall Details

Choose Cortex Plugin 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).
You have access to required keys: MEMEM_TELEMETRY_SOURCE.
Primary tools included: Event-triggered background miner extracting durable lessons from conversations, Stores memories as markdown files in a local Obsidian vault, Active Memory Slice assembling query-tailored context briefings.

Feature & Specification Comparison

Specification	Memocall baodq06 Knowledge & Memory	Cortex Plugin TT-Wang Knowledge & Memory
Summary	Recall past Claude Code conversations from any project. Lists and searches your sessions, then loads one on demand as clean, compact Markdown — with outline, turn-range, and in-session search for large sessions. Read-only over local /.claude transcripts; collapses tool calls to stay under the context cap. npx -y memocall	Persistent, self-evolving memory plugin for Claude Code. Background miner extracts durable lessons (decisions, conventions, bug fixes) from completed sessions via Claude Haiku, stores them as human-readable markdown in an Obsidian vault, and assembles query-tailored context briefings at session start. Local-first, no cloud, no API keys. Self-healing install via uv bootstrap shim, /cortex-doctor preflight, graceful FTS-only degraded mode when claude CLI missing. MIT.

Tools & Capabilities Breakdown

Memocall Tools (6)

Reads local ~/.claude/projects transcript files only

Returns compact Markdown with tool call outputs elided

Supports session listing, searching, loading, outlining, and in-session search

Handles large sessions with outline and turn-range loading

Read-only, no network or telemetry

Integrates with Claude Code MCP tooling

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

Memocall Configuration

mcpServers (Claude Desktop / Cursor)

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

Cortex Plugin Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tt-wang-cortex-plugin": {
      "command": "pipx",
      "args": [
        "install",
        "memem"
      ],
      "env": {
        "MEMEM_TELEMETRY_SOURCE": "YOUR_MEMEM_TELEMETRY_SOURCE_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Memocall More alternatives to Cortex Plugin Knowledge & Memory category hub