Claudex vs Cortex Plugin — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Claudex vs Cortex Plugin
In-depth architectural comparison of the Claudex 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
Claudex
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Cortex Plugin
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Claudex 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 Claudex 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: Persistent structured memory with CRUD and TTL, SQLite FTS5 full-text search with advanced filters, Universal support for all Claude Code template versions.
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.
Persistent memory + FTS5 full-text search for Claude Code conversation history. Indexes /.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, list sessions, get summaries) plus prompts. Includes a web UI for visual exploration with themes and exports. Works with Claude Code, Cursor, Codex, Windsurf, and any MCP-compatible client. npm install -g @kunwarshah/claudex
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
Claudex Tools (6)
Persistent structured memory with CRUD and TTL
SQLite FTS5 full-text search with advanced filters
Universal support for all Claude Code template versions
Smart rendering of code, markdown, diffs, and JSON
Session analytics dashboard with charts and stats
Web UI with 10 themes, 29 fonts, and export options
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).
Claudex is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Cortex Plugin belongs to Knowledge & Memory using local stdio subprocess. Select Claudex when you need capabilities focused on knowledge & memory and Cortex Plugin when you require tools for knowledge & memory.