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.

DimensionOpen Agent BuilderVisual workflow builder for AI agents powered by FirecrawlMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS27 / 100 · D79 / 100 · B
Reliability2 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance7 / 2016 / 20
Documentation8 / 2018 / 20
Setup experience4 / 2015 / 20
Best for
  • Developers and teams wanting to visually build AI agent workflows
  • Users needing integration with Firecrawl for web scraping
  • Users wanting to use Anthropic Claude's MCP tool support
  • Workflows requiring real-time execution and streaming updates
  • 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 needing simple scripts without a visual interface
  • Users needing full MCP support with OpenAI or Groq (currently limited)
  • Users wanting to deploy as a standalone MCP server rather than an application
  • 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
  • Requires Firecrawl API key and network access for scraping
  • Requires LLM API keys (e.g., Anthropic, OpenAI, Groq)
  • Requires Convex database and Clerk authentication for deployment
  • Optional E2B key for sandboxed code execution
  • 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
  • Project is actively developed; some features may be unstable
  • Dependency on external services (Firecrawl, Convex, Clerk) costs and availability
  • Exposure of LLM and Firecrawl API keys; must be managed securely
  • Supply chain risk: relies on many third-party npm packages; review dependencies
  • 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