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.

DimensionBonsai MCPMCP integration for IFC via Blender and Bonsai.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS51 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Architects, engineers, and BIM professionals needing IFC model access.
  • LLM developers who want to interact with IFC data.
  • Automating design reviews and documentation generation.
  • 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 not using Blender or the Bonsai BIM addon.
  • Processes requiring full automation without human interaction.
  • Users unfamiliar with IFC models (learning curve).
  • 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
  • Execute commands on a local Blender instance via the addon server.
  • Execute arbitrary Python code in Blender (execute_blender_code).
  • Access and modify local IFC files.
  • Capture Blender viewport images and export data files.
  • 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 unwanted changes.
  • Performance issues with large IFC models.
  • Misconfiguration in Docker deployments, leading to connection failures or CORS issues.
  • 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, Open WebUIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools170