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.

DimensionCloudflare AgentsOfficial Cloudflare SDK for building persistent, stateful AI agents on Durable Objects, with optional MCP server/client support as one of many built-in features.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS56 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • TypeScript developers building stateful AI agents on the Cloudflare Workers/Durable Objects platform
  • Teams that want to expose their own agent capabilities as an MCP server
  • Builders needing an integrated stack of scheduling, WebSockets, voice, and workflows for agentic apps
  • 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 looking for a turnkey MCP server with a fixed tool list to drop straight into a Claude Desktop config
  • Teams not deploying to Cloudflare Workers/Durable Objects
  • External contributors hoping to land code via pull request (the repo currently does not accept external PRs)
  • 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
  • A Cloudflare account with SQLite-backed Durable Objects enabled
  • Workers deployment and binding configuration permissions
  • Additional credentials/bindings depending on features used (e.g. AI model calls, email service)
  • 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
  • MCP server/client behavior is implemented by the developer, so missing authorization checks could expose agent state or callable methods
  • Code Mode and sandboxed execution run LLM-generated code — misconfigured isolation could introduce execution risk
  • Incorrect Durable Object bindings or SQLite migration tags can cause state loss or failed migrations
  • The repo does not accept external PRs, so community-reported issues depend entirely on Cloudflare's own fix timeline
  • 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