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.

DimensionBlockbench MCPAdds an MCP server to Blockbench so AI clients can reach a local modeling sessionMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS56 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • 3D modelers using the desktop version of Blockbench
  • Developers who want MCP clients wired into their local modeling environment
  • Users adding AI assistance to a Blockbench workflow
  • 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 who cannot run desktop Blockbench or load plugins
  • Clients without access to local HTTP endpoints
  • Users who need official support or a hosted service
  • 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
  • Loading and running a third-party plugin inside Blockbench
  • Exposing a local MCP server port (default 3000)
  • AI client access to http://localhost:3000/bb-mcp
  • 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 plugin is third-party and not maintained by Blockbench itself
  • A local MCP endpoint without restrictions could be reached by other local programs
  • Incorrect port or endpoint configuration causes connection failures
  • Loading the plugin from a URL relies on remote script distribution
  • 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 clientsVS Code, Claude Desktop, Claude Code, Cline, Ollama, OpenCode, AntigravityClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00