M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionQMD MCP ServerA local hybrid search engine for Markdown knowledge bases.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS56 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance8 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Users who want documents and model processing to remain local
  • Individuals and teams with Markdown documents, meeting records, or code documentation
  • Agent workflows that benefit from combined keyword and semantic search
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users seeking hosted cloud search, remote knowledge-base synchronization, or built-in authentication
  • Environments without resources to run local models or download GGUF files
  • Use cases involving files outside configured collections or unsupported indexed content
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Read access to configured collection files for indexing and document retrieval
  • Write access to local QMD configuration, cache, SQLite index, and model-cache locations
  • Network access to download GGUF models from HuggingFace on first use; collection update hooks may also execute configured shell commands
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • HTTP endpoints are unauthenticated by default; add an authentication layer before binding the server to a non-local address
  • The index may contain personal notes, meeting transcripts, or internal documentation, so local index files and HTTP access require protection
  • Configured collection update commands execute through bash in the collection directory and can abort subsequent updates on failure
  • Custom project-local configuration can reference paths outside the project or custom models; untrusted fields are skipped in non-interactive environments
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Claude CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools40