Skip to main content
Glama
YonggangG

zemax-mcp

by YonggangG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to zemax-mcp

No user-submitted related servers found.

    Related Servers

    • zemax-mcp

      dongzhaohe321418-lab
      F
      license
      Not graded
      quality
      B
      maintenance
      Safety-first MCP server enabling AI assistants to drive Zemax OpticStudio sequential-mode optical design workflows, including a mock backend for validation.
      1
      -

    • SolidWorks MCP Bridge

      Said-AER
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that integrates local LLMs (via Ollama) with SolidWorks through its COM API, enabling read-only inspection of features, dimensions, equations, mass properties, and file exports. It supports models like Qwen3 and plans future expansion to editing and generation.
      -

    • mcp-opentym

      doanhtuan123
      F
      license
      Not graded
      quality
      F
      maintenance
      A lightweight MCP HTTP server giving AI assistants real tools to interact with your Windows machine, including running commands, file access, system info, web search, and browser automation.
      1
      -

    • WinBridgeAgent

      codyard
      A
      license
      Not graded
      quality
      C
      maintenance
      An open-source MCP server for Windows that provides traceable system operations (file, screenshot, clipboard, process, power management) to AI assistants via HTTP/SSE.
      12
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 143 tools

    Disambiguation2/5

    Many tools overlap heavily, including legacy wrappers alongside modern equivalents (e.g., zemax_set_surface vs zemax_lde_set_surface, zemax_optimization_wizard vs zemax_merit_wizard) and multiple spot/MTF/detector variants. Descriptions sometimes clarify legacy status, but the boundaries remain unclear and misselection is likely.

    Naming Consistency4/5

    Almost all tools use a consistent zemax_ prefix and snake_case, and getter/setter pairs follow predictable verb_noun patterns. However, many analysis tools use noun phrases (e.g., zemax_fft_mtf, zemax_ray_fan) and legacy wrappers introduce minor naming deviations.

    Tool Count1/5

    With 143 tools, this server is far beyond any reasonable MCP tool surface, even for a complex optical design domain. The set includes many legacy wrappers and overlapping analysis/detector variants, making it an extreme mismatch rather than a well-scoped collection.

    Completeness5/5

    The surface covers sequential and non-sequential systems, surface/object CRUD, optimization, tolerancing, numerous analyses, file lifecycle, and configuration handling. No obvious core gaps are apparent for the stated optical design purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources