LINZA MCP vs Cortex Plugin — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
LINZA MCP vs Cortex Plugin
In-depth architectural comparison of the LINZA MCP 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
LINZA MCP
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Cortex Plugin
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose LINZA MCP 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 LINZA MCP 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: LINZA_VAULT.
Primary tools included: Local SQLite index at .linza/linza.db, Markdown, TXT, JSON, DOCX, and XLSX support, Optional local PDF extraction.
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.
Local-first review-gated sidecar for Markdown workspaces. Indexes notes and incoming artifacts into SQLite, proposes domains, links, memory, and growth cards with evidence, and keeps source files unchanged until explicit review. pip install linza-mcp
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
LINZA MCP Tools (6)
Local SQLite index at .linza/linza.db
Markdown, TXT, JSON, DOCX, and XLSX support
Optional local PDF extraction
Evidence-backed review intents
Dry-run and explicit apply workflow
Context packages with sources and relationships
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).
LINZA MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Cortex Plugin belongs to Knowledge & Memory using local stdio subprocess. Select LINZA MCP when you need capabilities focused on knowledge & memory and Cortex Plugin when you require tools for knowledge & memory.