Skip to main content
Glama
Sign In
tigl-mcp

tigl-mcp

by cmudrc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tigl-mcp

No user-submitted related servers found.

    Related Servers

    • cityjson-mcp

      Yarroudh
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to inspect, validate, transform, and query CityJSON models, with support for conversion, persistence, and 3D geometry validation.
      42
      3
      MIT

    • Battenmark

      halsyourpal422
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.
      1
      Apache 2.0

    • Plasticity MCP

      Sparrow51
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to inspect and measure native B-rep geometry, create and edit CAD models, export results, and optionally review models or prepare print jobs locally.
      11
      MIT

    • root-ext-cad

      graphgrow
      F
      license
      A
      quality
      B
      maintenance
      CAD-engineering MCP tool server for parametric modeling, DFM validation, mechanical calculations, and more. Enables code-CAD builds (build123d/CadQuery), model inspection, meshing, and mechanical calculators via MCP stdio.
      11
      -

    • mechanical-visual-truth

      ufukefekaya-tr
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables users to create and manage workspace-scoped CAD contracts, build and validate STEP-backed geometry, generate technical drawings and proof renders, audit models, and sample motion through bounded MCP tools.
      -
    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

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool maps to a distinct action or resource: session lifecycle (open/close/ping), inspection (summary, list, metadata, parameters), validation (check_geometry), and export (mesh vs CAD). The only mild overlaps are get_configuration_summary vs list_geometric_components and export_component_mesh vs export_configuration_cad, but the descriptions clearly separate them by scope (overview vs enumeration) and by output form (base64 mesh vs file-path CAD).

    Naming Consistency4/5

    Nearly every name follows a consistent snake_case verb_noun pattern (get_configuration_summary, open_cpacs, close_cpacs, check_geometry, list_geometric_components, set_high_level_parameters). The only deviation is the bare verb 'ping', which is a conventional exception rather than an inconsistency.

    Tool Count5/5

    Eleven tools fit cleanly into the 3-15 well-scoped range for a CPACS/TiGL geometry server. Each tool corresponds to a distinct stage of the workflow (open a session, inspect, validate, export), and none appears redundant.

    Completeness4/5

    The surface covers the full session lifecycle, component inspection, geometry validation, mesh/CAD export, and parameter read/write, which is solid coverage for the stated domain. The main gap is that set_high_level_parameters explicitly does not modify geometry, so there is no path for applying parameter changes or re-evaluating the shape, which limits a natural design-iteration workflow.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources