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.

DimensionAutoCAD MCP ServerMCP server for AutoCAD LT automation and headless DXF generationMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS46 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance7 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Engineers and designers needing to automate AutoCAD LT (Windows)
  • Developers who want to generate DXF without AutoCAD
  • Process industry applications integrating with CTO P&ID symbol library
  • 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 for AutoCAD LT on Mac (does not support AutoLISP)
  • Not for users needing 3D operations or Express Tools (LT limitations)
  • Not for users needing ActiveX/COM (vlax-*) functionality
  • 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 access to AutoCAD LT window messaging (PostMessageW)
  • Needs read/write access to C:/temp (IPC directory, configurable)
  • Allows execution of arbitrary AutoLISP code (execute_lisp)
  • Requires access to CTO P&ID symbol library if using pid tools
  • 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
  • Sending keystrokes to AutoCAD may interfere with current drawing; save work regularly
  • execute_lisp can run arbitrary code, posing security risks
  • IPC timeouts may cause command failures; adjust environment variables
  • File IPC backend requires native Windows Python; WSL needs special configuration
  • 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, Claude CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools80