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.

DimensionMCP PromptsLocal MCP server for storing and serving reusable AI prompts and agent templates.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS51 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance7 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers maintaining a personal or team library of prompts and agent templates
  • Users of Claude Desktop/Cursor who want prompt management exposed as an MCP tool
  • Projects using claude CLI orchestration with specialized subagents
  • 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
  • Teams needing a hosted/multi-tenant prompt service (enterprise AWS features live in a separate archived module)
  • Users wanting database-backed prompt storage (prompts are plain JSON files)
  • Non-technical users unfamiliar with configuring MCP client JSON files
  • 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
  • Local filesystem read/write access to the configured PROMPTS_DIR
  • Ability to execute the Node.js server process
  • The orchestration script additionally invokes the local claude CLI
  • 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
  • Prompts and agent templates are stored as plain JSON files with no access control described
  • create_prompt/update_prompt/delete_prompt let a connected client modify or remove local files with no confirmation step described in the README
  • No authentication mechanism is documented for the stdio server itself
  • Enterprise/AWS deployment features exist but are only referenced as archived, without detail in the main README
  • 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, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools70