epanet-mcp-server
Related Servers
Alternatives to epanet-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to load, simulate, inspect, and edit EPANET hydraulic/water-quality models locally via stdio.33MIT
- AlicenseAqualityAmaintenanceEnables AI agents to design, connect, and simulate water-handling systems from tested physical component models, with typed tools and physics-based warnings.20Apache 2.0

idfkit-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to create, edit, and simulate EnergyPlus building energy models via natural language. Supports schema exploration, model editing, simulation execution, and documentation search.393MIT- AlicenseBqualityDmaintenanceAn 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.187MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to read and modify the EPLAN Electric P8 data model through MCP, including listing pages, reading devices and parts, copying circuits, renaming tags, and fixing texts.MIT
- AlicenseNot gradedqualityFmaintenanceA water treatment process simulation engine that exposes WaterTAP capabilities through MCP and CLI adapters, enabling AI agents to build, solve, and optimize flowsheets using natural language.1MIT
TDQS
Scored across 44 tools
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.
All tool names follow a consistent verb_noun pattern with underscores, such as 'get_*', 'set_*', 'create_*'. No mixing of conventions.
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.
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.