openmep
Related Servers
Alternatives to openmep
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate drafting end to end — drawing mechanical parts, P&IDs, and architectural plans, then verifying measurements against source requirements, critiquing quality, and delivering DWG/DXF files. Runs live through COM on Windows or headless anywhere via ezdxf, exposed as typed tool packs so clients only load the capabilities they need.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to draft, read, validate, diff, and take off CAD drawings through a single typed contract served by either a live COM session or a headless ezdxf engine. Ships 247 tools covering P&ID, mechanical, and architectural drafting, with ISO GD&T and dimension-tolerance validation plus spec-to-drawing and takeoff-to-workbook workflows.-
- AlicenseAqualityBmaintenanceProvides deterministic data-center field calculations through MCP tools for liquid-loop hydraulics, SOP/MOP/EOP procedure classification, and ANSI/ISA-71.04 corrosion coupon classification. Coding assistants can call it while drafting design notes, commissioning scripts, MOPs, and handover reviews.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to generate and locally edit parametric architectural DXF files, run geometry checks and rectangular layout solving, and use traceable research and professional-learning workflows; on Windows it can also attach to a running AutoCAD for guarded read/write operations.6MIT
- AlicenseAqualityCmaintenanceEnables AI agents to run deterministic data-center engineering calculations and commissioning audits, including liquid-cooling hydraulics, pipe friction and flow checks, corrosion severity classification, protocol search, and defect-code lookup.62MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate, inspect, edit, audit, and export electrical distribution CAD drawings—including medium/low-voltage plans and EPM/RETIE/NTC 2050 compliance checks—through 24 precision tools over stdio JSON-RPC.MIT
TDQS
Scored across 2 tools
The tools operate at different scopes: size_duct handles a single duct run, while size_duct_network sizes an entire network with multiple segments. The names are similar but the descriptions clearly differentiate their purposes, making confusion unlikely for an agent.
Both tool names follow a consistent verb_noun pattern (size_duct, size_duct_network). The only minor issue is that the noun part is very similar, but the naming convention itself is consistent.
With only 2 tools, the server is quite thin for a duct sizing domain. While each tool is well-scoped, the limited count may force agents to rely on external knowledge for common tasks like equipment selection or duct material properties.
The surface covers core duct sizing operations but lacks obvious complementary tools such as equipment selection, pressure loss calculations for fittings beyond equivalent length, or output formatting. Notably, there is no tool to retrieve or list existing duct networks, which could be a gap for iterative design workflows.