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.

DimensionHoudini MCP ServerConnect SideFX Houdini to Claude via the Model Context Protocol.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS28 / 100 · D79 / 100 · B
Reliability4 / 2012 / 20
Security and permissions2 / 2018 / 20
Maintenance6 / 2016 / 20
Documentation8 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Houdini artists and technical directors who want a seamless workflow between Claude and Houdini.
  • Users interested in AI-assisted procedural 3D modeling and scene generation.
  • Developers familiar with MCP who want to extend Claude to work with 3D tools.
  • 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 a Houdini license (requires SideFX Houdini).
  • Users seeking official support (this server is not maintained by SideFX or Anthropic).
  • Users wanting a remote server without local Houdini access (the server runs on localhost).
  • 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
  • Local network access: listens for TCP connections on localhost:9876.
  • File system access: reads and writes files in the Houdini configuration directory.
  • Execution permission: executes Python code within the Houdini context.
  • 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 untrusted code in Houdini can lead to data loss or system damage; only use in trusted environments.
  • Running a server on localhost may expose it to other local processes; ensure no malicious software.
  • OPUS integration requires a RapidAPI key, which if mishandled could leak sensitive information.
  • 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
Tools00