Skip to main content
Glama
macery12

Stormworks MCP

by macery12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Stormworks MCP

No user-submitted related servers found.

    Related Servers

    • SolidWorks MCP Server

      Sam-Of-The-Arth
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to create and manipulate SolidWorks CAD models through natural language commands, automating part creation, sketching, and extrusion.
      10
      -

    • MC-Schema-MCP

      Nek0cha
      F
      license
      B
      quality
      B
      maintenance
      Enables designing Minecraft structures through Claude Code and exporting them as Sponge Schematic v3 (.schem) files.
      14
      -

    • 3DP MCP Server

      brs077
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to create 3D-printable CAD models using build123d, with tools for modeling, modification, analysis, and publishing to platforms like Thingiverse and GitHub.
      14
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • 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
    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.9/5.0

    Scored across 50 tools

    Disambiguation3/5

    Several tool clusters overlap: analyze_vehicle vs analyze_land_vehicle vs analyze_hull, preview_vehicle vs preview_game_vehicle vs inspect_view vs open_in_viewer, and search_parts vs search_land_parts vs query_parts. The detailed descriptions clarify contexts, but an agent could still misselect within these families, especially for preview and analysis tasks.

    Naming Consistency4/5

    Most tools follow a snake_case verb_noun pattern (list_*, get_*, query_*, edit_*, preview_*, save_*). A few deviate by using noun phrases or unusual forms (complaint, deck_profile, hull_design_guide, land_vehicle_guide, open_in_viewer), but the overall convention is readable and predictable.

    Tool Count2/5

    50 tools is heavy for a single MCP server, even for a complex domain like Stormworks vehicle design. Many tools could be consolidated or split into sub-servers (e.g., hull design, land design, part editing, validation, previews). The count exceeds the practical sweet spot and increases selection burden.

    Completeness4/5

    The surface covers hull and land vehicle design, part editing, connection routing, validation lifecycle, previews, and complaint reporting very thoroughly. Minor gaps exist such as no explicit delete/rename design tool and no aircraft-specific design guide, but core workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources