OpenMEP duct sizing MCP server

by samarmstrong·io.github.samarmstrong/openmep·v0.2.0

No reviews yet

Deterministic HVAC duct sizing at a fixed or Manual D friction rate; grades existing ducts.

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

Growing

0 stars62 downloads/wk

Reviews

Write one

Nobody has reviewed OpenMEP duct sizing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

OpenMEP duct sizing tools (2)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

size_duct
Recommend a standard round diameter for one duct run carrying a given CFM, with velocity and friction at that size.
size_duct_network
Size every supply, return, exhaust, and outside-air segment of a connected duct network. Each terminal's requiredCfm

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings

Code scan6 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 26 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How OpenMEP duct sizing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 92/100; higher than 95% of 48,255 servers
Tools: 2; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 62; more than 50% of 12,191 servers with a package

What its tools let an agent do: 2 read

Release history: 2 versions in the registry since 2026-09-22, latest 2026-10-07, typically one every 15 days.

Install OpenMEP duct sizing in Claude Code, Cursor or VS Code

Runs npx -y @openmep/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add openmep -- npx -y @openmep/mcp

Add to Cursor

What the publisher says

From the OpenMEP duct sizing repository's README, as published. We do not edit it. Read it on GitHub

OpenMEP

Open MEP building state that a language model can reason about and edit correctly — grounded in deterministic loads and duct sizing, graded by a deterministic checker.

The bet: the useful unit of AI-assisted HVAC design is not a Revit plugin but a small, inspectable data model (rooms, loads, terminals, ducts, connectivity, constraints) that deterministic engines compute over and agents edit. This repo is that model, the engines, and the harness that measures whether an agent can edit it without breaking it.

What is here

Real-model tests and evals run on public IFC fixtures (buildingSMART Duplex and WBDG Office ARCH + MEP pairs, CC BY 4.0) fetched by fixtures/fetch-public-ifc.sh; see fixtures/README.md for provenance and the exporter quirks the pipeline handles. No IFC is committed to this repository.

Quick start

Give an agent a duct-sizing tool

claude mcp add openmep -- npx -y -p @openmep/mcp openmep-mcp

Any MCP client works ({"command": "npx", "args": ["-y", "-p", "@openmep/mcp", "openmep-mcp"]}). Describe the system in plain language, with the CFM each terminal needs, and the agent calls the engine; see packages/mcp/README.md.

Size a duct network from JSON (no editor required)

npx -p @openmep/hvac-domain openmep-hvac size packages/hvac-domain/examples/furnace-two-registers.items.json --pretty
npx -p @openmep/hvac-domain openmep-hvac duct --cfm 250 --role main --diameter-in 6

From a checkout: npm ci && npm run build --workspace @openmep/hvac-domain, then node packages/hvac-domain/bin/openmep-hvac.js ....

The network is a list of equipment, fittings, terminals with engineer-supplied requiredCfm, and segments linked by connectedItemRefs. The result lists each run's system, CFM, role, recommended standard round diameter, velocity and friction rate, grades any existing section as ok/undersized/oversized, and reports terminals with no airflow or no path to equipment. Any host that can produce this document gets the same engine; openmep-pascal items produces it from a Pascal scene.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

OpenMEP duct sizing: common questions

Is OpenMEP duct sizing MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the OpenMEP duct sizing safety report
How do I install OpenMEP duct sizing?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does OpenMEP duct sizing need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is OpenMEP duct sizing maintained?: The last commit was 27 days ago (2026-10-07). The latest release is v0.2.0.
How does OpenMEP duct sizing compare with other MCP servers?: safety score 92/100 (higher than 95% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.