Skip to main content
Glama
Sign In
waterjet

waterjet

by vazluis83
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to waterjet

No user-submitted related servers found.

    Related Servers

    • PI Doc MCP

      nurnaufal321
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that gives AI assistants direct access to live AVEVA PI System documentation, eliminating hallucination on PI-specific topics.
      3
      MIT

    • festo-codesys-mcp

      efranceschetti
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that turns AI assistants into competent Festo/CODESYS PLC engineers by grounding them in curated, manufacturer-accurate knowledge and forcing every artifact through a machine-checked validation pipeline for CODESYS import.
      16
      18
      65 npm
      2
      MIT

    • Shared Knowledge MCP Server

      j5ik2o
      A
      license
      Not graded
      quality
      D
      maintenance
      This server enables AI assistants (CLINE, Cursor, Windsurf, Claude Desktop) to share a common knowledge base through Retrieval Augmented Generation (RAG), providing consistent information access across multiple tools.
      4
      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

    A3.5/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have a clearly distinct target: procedures, drawings, pages, sheets, axes, drive parameters, PLC I/O, components, parts and pump flow are all separable, and descriptions actively steer selection ("call this first", "use list_procedures for the ids"). The main friction is that dump_machine_data re-packages subsets of machine_overview, get_axis, get_plc_io, get_pump_info and list_procedures, and that global search overlaps with find_component/search_parts/find_sheet, so an agent may pick the wrong entry point for a lookup.

    Naming Consistency4/5

    The dominant pattern is verb_noun (list_procedures, get_procedure, get_drawing, get_page, get_page_image, get_axis, get_plc_io, find_component, search_parts, get_pump_info, compare_drive_parameters, explain_drive_parameter). A few deviate into bare nouns or odd forms (machine_overview, nozzle_flow, get_sheet_index, dump_machine_data), but nothing is chaotic and the intent is always readable.

    Tool Count4/5

    22 tools is on the heavy side, but the domain genuinely spans documents, CAD drawings, electrical schematics, drive parameter files, PLC I/O, spare parts and pump hydraulics, so each tool maps to a real subject area. A couple of pairs (list_documents/list_drawings, find_sheet/get_sheet_index) could be consolidated without losing capability.

    Completeness4/5

    Coverage of a technical documentation/knowledge base is strong: overview, document listing, full-text search, page text and images, procedures, drawings, axes, drive parameters (get/diff/explain), PLC I/O, component lookup, spare parts and nozzle flow calculations. Minor gaps remain — no alarm/fault-code troubleshooting tool despite alarm thresholds being mentioned, and drawing retrieval is split (get_drawing handles CAD only, PDF drawings require get_page_image).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources