Skip to main content
Glama
MERURUXD

CODE V MCP

by MERURUXD

Related Servers

Alternatives to CODE V MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      A Windows-only MCP server that enables AI assistants to automate Ansys Zemax OpticStudio through the ZOS-API, exposing sequential and non-sequential mode, analysis, optimization, glass, tolerancing, configuration, and lifecycle operations. It supports stdio, SSE, and Streamable HTTP transports, with per-tool capability statuses distinguishing live-verified, offline-implemented, and scaffolded functionality.
      2
      143
      2
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to create and edit technical drawings, manage layers and geometry, process GIS/research mapping data, generate previews and layouts, and automate AutoCAD documents on Windows through COM.
      225
      50 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables automated data import, analysis, graphing, and project management for Origin/OriginPro through a hardened MCP interface with constrained file access and optional expert LabTalk mode.
      24
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to connect to and automate AutoCAD on Windows via COM, exposing tools to inspect drawings and layers, create geometry and text, manage system variables, run commands, and save or open drawings. Requires full AutoCAD running with a drawing open.
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools mostly target distinct actions, but get_status overlaps with get_lens and get_analysis for state reporting, and open_lens vs get_lens both return lens details. update_lens and edit_lens_structure also require care to distinguish parameter edits from structural edits, though the detailed descriptions help.

    Naming Consistency4/5

    All names use snake_case with a verb-first pattern, e.g. get_status, open_lens, run_analysis. Minor deviations like edit_lens_structure (verb_noun_noun) and save_lens_as (preposition) keep it from perfect consistency.

    Tool Count5/5

    11 tools is well-scoped for a session-based optical design server, covering session lifecycle, lens open/create/read/update/structure-edit/save, and analysis run/get/cancel. Each tool appears to earn its place without redundancy.

    Completeness4/5

    Core workflows for simple single-zoom lenses and analyses are covered: open, create, get, update, structural edit, save as, close, and full analysis lifecycle. However, there is no delete-lens or in-place save tool, and recovery points cannot be restored, leaving minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues