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 Workers Next.js SaaS TemplateA complete Next.js SaaS template for Cloudflare Workers, featuring authentication, subscription billing, and an AI agent platform (including MCP)MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS43 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Developers who want to rapidly bootstrap a SaaS product with a built-in AI platform and MCP functionality
  • Teams that need comprehensive authentication and authorization for AI agents (OAuth, API keys)
  • 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
  • Simple projects that do not need AI agent features or an MCP server
  • Deployments that require a Node.js server instead of Cloudflare Workers
  • 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 a Cloudflare account and relevant Worker bindings (D1, KV, R2, AI, etc.)
  • Requires a Stripe account and API keys to enable billing features
  • Requires configuring Turnstile keys for CAPTCHA
  • 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
  • The template is experimental; Vinext and Cloudflare's MCP components may change
  • The MCP server allows AI agents to access your public API's power; if API keys or OAuth credentials leak, it could lead to unauthorized access
  • Deployment configuration is complex and requires careful setting of environment variables and bindings
  • 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, Claude.ai, ChatGPT, Cursor, VS Code, Codex, Antigravity, Grok CLIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools10