LINZA MCP vs Enquire MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
LINZA MCP vs Enquire MCP
In-depth architectural comparison of the LINZA MCP and Enquire MCP 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
Enquire MCP
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose LINZA MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Enquire MCP 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.
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
Long-term memory for AI agents (Claude Code/Desktop, Cursor, ChatGPT, Codex, OpenClaw) backed by a local Obsidian markdown vault. Hybrid retrieval (BM25 + ML embeddings + BGE reranker, RRF-fused), HNSW + int8 quantization, agentic RAG (HyDE + sub-question), GraphRAG-light (Louvain wikilink community detection), standalone Obsidian Bases, PDFs + Tesseract OCR. 46 tools, 19 MCP prompts, MIT, SLSA L2, zero cloud calls during serve. npx -y @oomkapwn/enquire-mcp serve --vault
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
Enquire MCP Tools (6)
Hybrid retrieval: BM25, ML embeddings, BGE reranker with RRF fusion
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, Enquire MCP belongs to Knowledge & Memory using local stdio subprocess. Select LINZA MCP when you need capabilities focused on knowledge & memory and Enquire MCP when you require tools for knowledge & memory.