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.

DimensionAgentpackLocal-first task-state ledger for AI coding agentsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS68 / 100 · C79 / 100 · B
Reliability11 / 2012 / 20
Security and permissions16 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who need task continuity between AI coding agent sessions
  • Teams that prefer local, reviewable files over cloud services
  • Users of Claude Code, Cursor, or Codex seeking consistency across sessions
  • 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 cloud sync or collaboration features (it is local-first)
  • Users not on Node.js 20+ or who prefer a single binary
  • Those who want integration with issue trackers or project management tools (not provided)
  • 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
  • Access to the local repository filesystem (reads/writes .agentpack/)
  • Global npm package installation (agentpack-cli)
  • May configure git hooks or client hooks for task gating
  • 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
  • Mistakes in task state could lead to incorrect assumptions by agents
  • Local files could be accidentally modified or lost
  • Secret redaction is best-effort and not guaranteed
  • Task gate could block legitimate edits if over-restrictive
  • 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 Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00