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.

DimensionBlender MCP ServerLet any LLM control Blender 3D scenes in real time via structured JSON commandsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS37 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation6 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • 3D artists who want real-time LLM-driven scene control in Blender
  • Developers and hobbyists driving Blender via natural language
  • Users needing an LLM-agnostic integration (GPT, Claude, local models)
  • 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 do not work with Blender
  • Those seeking an officially supported Blender tool (this is community-built)
  • Users who need a GUI-driven workflow rather than command-based control
  • 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 network/socket access to send JSON commands over TCP
  • Requires read/write control over Blender scenes and objects
  • 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
  • LLM-generated commands may unintentionally modify or damage the current Blender scene
  • TCP socket communication could be exposed on the local network if not secured
  • The README does not document authentication, so security hardening must be assessed independently
  • 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