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 Open MCPControl Blender 3D with natural language via local AI modelsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS40 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions3 / 2018 / 20
Maintenance6 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • 3D artists who want to control Blender with local AI models
  • Developers who need to automate 3D workflows
  • Users integrating with Claude Desktop or Cursor for AI-assisted modeling
  • 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 without local Ollama or ability to run local LLMs
  • Users needing cloud AI services (since it uses local models)
  • Users unfamiliar with Blender add-on installation
  • Users requiring official support (non-official project)
  • 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
  • Can read and modify Blender scene (objects, materials, transforms)
  • Can execute arbitrary Python/bpy code via blender_execute_code
  • Can delete objects via blender_delete_object
  • Can render images to files
  • Can access internet to download PolyHaven assets
  • Can access local models via Ollama
  • Requires network ports (8000, 9876, 11434)
  • 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
  • Executing arbitrary code may corrupt scenes or systems if given malicious prompts
  • Deleting objects is irreversible and may lose work
  • PolyHaven downloads require internet and may fail
  • Local LLM may generate inaccurate code; review before execution
  • Non-official project may have bugs or security vulnerabilities
  • 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 Desktop, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools160