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.

DimensionWorkflow OrchestratorDAG-based workflow orchestration with parallel execution and run historyMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS27 / 100 · D79 / 100 · B
Reliability4 / 2012 / 20
Security and permissions5 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation3 / 2018 / 20
Setup experience5 / 2015 / 20
Best for
  • Developers using Claude Code who need DAG-based automation
  • Teams that want deterministic, dependency-driven task execution
  • 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 real-time collaboration or human-in-the-loop decision tools
  • Scenarios where a simpler linear script is sufficient
  • 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
  • Runs as a local stdio process via the npm package @claude-code-plugins-plus/workflow-orchestrator
  • No explicit permission documentation is provided in the source
  • 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
  • Third-party community plugin — no official upstream maintainer
  • MIT-licensed, but the code is not audited in this profile
  • No server-specific security documentation in the source
  • 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 CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00