Skip to main content
Glama

Related Servers

Alternatives to epanet-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to load, simulate, inspect, and edit EPANET hydraulic/water-quality models locally via stdio.
      33
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to design, connect, and simulate water-handling systems from tested physical component models, with typed tools and physics-based warnings.
      20
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create, edit, and simulate EnergyPlus building energy models via natural language. Supports schema exploration, model editing, simulation execution, and documentation search.
      39
      98 PyPI
      14
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides a toolbox for interacting with EPA SWMM stormwater models, enabling users to analyze model data and interpret results through LLM-driven tools. It assists stormwater modelers in understanding hydraulic systems and modeling behavior using natural language interfaces.
      18
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude-compatible assistants to design, calculate, and review building cold-water and sanitary-sewer networks according to ABNT NBR 5626/8160, including reading piping from DXF and producing calculation memorials, segment tables, and annotated DXF outputs.
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to plan, validate, generate, and deploy Cisco Packet Tracer network topologies from natural-language prompts, including routing, switching, DHCP, VLANs, security, IPv6, wireless, live deployment, verification, and .pkt project management.
      3
      MIT

    TDQS

    B3.3/5.0

    Scored across 45 tools

    Disambiguation4/5

    Tools split cleanly into getters, setters, simulation runners, and scenario creators, each targeting a distinct resource or action. A few boundaries blur, such as run_hydraulic_simulation vs run_full_simulation vs run_quality_simulation, and direct setters (set_pump_status) vs scenario wrappers (create_pump_control_scenario), but descriptions generally clarify the differences.

    Naming Consistency5/5

    Every tool follows a predictable snake_case verb_noun pattern: list_, get_, set_, create_, run_, add_, delete_, load_, unload_, save_. No mixed conventions or vague verbs appear.

    Tool Count2/5

    At 45 tools, the surface is well above the typical well-scoped range. Many granular setters and scenario creators could be consolidated (e.g., a generic set_link_attribute or parameterized scenario builder), making the set heavy for agents to navigate.

    Completeness3/5

    The surface covers loading, inspection, parameter modification, simulation, time queries, and several scenario types. However, there are no tools to add or delete network elements (junctions, pipes, pumps, valves, tanks), which is a notable gap for building or restructuring networks; scenario deletion is also absent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues