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 MCPOpen-source MCP server to connect Blender with any LLM for AI-assisted 3D modeling.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS59 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • 3D artists and modelers who want to interact with Blender via natural language to boost productivity.
  • Developers looking to integrate Blender into AI-driven workflows.
  • 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
  • Not suitable for automated environments that require strict security controls, as execute_blender_code allows arbitrary code execution.
  • Not ideal for users needing reliable real-time rendering or complex animations, as tools focus on scene creation and modification.
  • 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
  • Network access to the Blender socket port (default 9876) for the MCP server.
  • Ability to execute arbitrary Python code, which can access the file system and other system resources.
  • External API keys (Sketchfab, Hyper3D, Hunyuan3D) for asset downloads and model generation.
  • 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 execute_blender_code tool can run arbitrary code, potentially causing data loss or system damage. Always save your work before using it.
  • Poly Haven integration may download large assets, consuming bandwidth and storage.
  • When running remotely, network connectivity may expose the server.
  • Third-party APIs may have usage limits or costs.
  • 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 DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools140