epanet-mcp-server
Related Servers
Alternatives to epanet-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to load, simulate, inspect, and edit EPANET hydraulic/water-quality models locally via stdio.33MIT
- AlicenseAqualityBmaintenanceEnables 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.3998 PyPI14MIT- 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.188MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables 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.3MIT
TDQS
Scored across 45 tools
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.
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.
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.
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.