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.

DimensionBacklog.mdMarkdown-native Task Manager & Kanban visualizer for any Git repositoryMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS72 / 100 · B79 / 100 · B
Reliability11 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance17 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who want to collaborate with AI coding assistants while keeping human oversight at every stage
  • Teams needing a lightweight, file-based, local-first task management solution
  • Projects aiming to improve AI output quality through clear acceptance criteria and definitions of done
  • 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 centralized, server-based task management with user roles and permissions
  • Users needing complex workflow automation or deep integration with proprietary tools
  • Projects requiring real-time multi-user synchronization
  • 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 and write Markdown task files in the project repository
  • Read and modify local filesystem (tasks, configuration)
  • Optionally: perform Git operations (auto-commit, remote operations)
  • Run within the specified MCP roots or BACKLOG_CWD
  • 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
  • Potential inconsistency in field types or metadata if task files are hand-edited
  • Git operations may be required for some features; non-Git projects are limited to local operations
  • If the project is not initialized, the server may serve init-required resources until initialized
  • Cross-branch accuracy may be limited depending on configuration
  • 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, Kiro, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools20