Skip to main content
Glama
hedless

Onshape MCP Server

by hedless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Onshape MCP Server

No user-submitted related servers found.

    Related Servers

    • onshape-mcp

      gpambrozio
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to drive Onshape CAD with 87 tools for documents, part studios, sketching, solid features, assemblies, drawings, measurement, and export, including zero-configuration browser sign-in.
      87
      75 npm
      1
      MIT

    • onshape-mcp-codex

      dsh18235538266-crypto
      A
      license
      B
      quality
      C
      maintenance
      Enables OpenAI Codex to drive real Onshape parametric CAD via 69 tools for documents, sketches, features, assemblies, parametric updates, FeatureScript, vision, and export.
      69
      MIT

    • onshape-mcp

      kyle-nelson-berkeley
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to drive OnShape CAD through the REST API for parametric modeling, FeatureScript queries, and STL export/verification.
      MIT

    • Jarvis Onshape MCP

      farouk15160
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to create and modify real Onshape CAD models — sketches, extrudes, fillets, patterns, mates, and parametric variables — with every mutation returning structured status, warnings, and geometric deltas. Includes multi-view PNG rendering, image-reference decomposition, and drawing OCR so the agent can visually verify and iterate on parts and assemblies.
      MIT

    • ares_onshape_local

      ARES-23247
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to prepare, track and verify native editable Onshape CAD features through a signed-in browser session or your own API Explorer, while making zero outbound Onshape requests itself. It searches saved receipts, builds standard feature JSON, and checks saved results so CAD calls can be executed without consuming the annual API-call allowance.
      MIT
    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.3/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource and action, and the create/get/delete/set verbs make selection straightforward. However, list_documents and search_documents overlap in purpose, and get_document vs get_document_summary (plus get_elements) could cause an agent to pick the wrong one.

    Naming Consistency5/5

    All tool names use snake_case and nearly all follow a verb_noun pattern: create_*, get_*, list_*, set_*, delete_*, export_*. Even with 48 tools, the naming convention is highly predictable; exceptions like add_assembly_instance or eval_featurescript still fit the verb-first style.

    Tool Count2/5

    48 tools is well beyond the 25+ threshold and feels over-fragmented for an MCP surface. Several sets, such as create_sketch_line/circle/arc/rectangle and the four mate creators, could be consolidated into parameterized operations without losing clarity.

    Completeness3/5

    The server covers document discovery, part studio feature creation, assembly construction, mates, export, and screenshots—so the core CAD workflow is present. However, there are notable lifecycle gaps: no update or delete for documents, no removal of assembly instances, and no way to edit existing features besides deleting them.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources