Skip to main content
Glama
Applied-Artificial-Intelligence-Eurecat

epanet-mcp-server

by Applied-Artificial-Intelligence-Eurecat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to epanet-mcp-server

No user-submitted related servers found.

    Related Servers

    • EPANET MCP Server

      hjlrosales
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to load, simulate, inspect, and edit EPANET hydraulic/water-quality models locally via stdio.
      33
      MIT
    • idfkit-mcp by idfkit

      idfkit-mcpofficial

      idfkit
      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
      3
      MIT

    • SWMM-MCP

      kLabUM
      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
      7
      MIT

    • OpenDSS MCP Server

      ahmedelshazly27
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables conversational power system analysis by connecting Claude AI with EPRI's OpenDSS simulator. Allows distribution planning engineers to perform sophisticated electrical grid studies through natural language instead of complex scripting.
      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 44 tools

    Disambiguation4/5

    Most tools have distinct purposes, but the multiple simulation run tools (run_hydraulic_simulation, run_quality_simulation, run_full_simulation) could cause confusion. Descriptions are clear enough to differentiate, but overlap exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores, such as 'get_*', 'set_*', 'create_*'. No mixing of conventions.

    Tool Count2/5

    With 44 tools, the set is overly large. While the domain is complex, many tools are repetitive (e.g., many set_* tools) and could be consolidated. This exceeds the recommended range for well-scoped servers.

    Completeness3/5

    The tool set covers loading, inspection, modification, and simulation well, but lacks tools for creating or deleting network elements (e.g., pipes, junctions). This is a notable gap for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources