muni-dev-cost 🏗️

What will the city and utility charge me to build here?

muni-dev-cost is an MCP server (and a pay-per-call x402 API) that gives an AI agent the municipal development cost for a US jurisdiction — the impact/development fees, water & sewer tap (connection) fees and capital-recovery charges a real-estate developer must pay before breaking ground — aggregated and normalized from public, government-published fee schedules into one comparable number.

For a real-estate development-feasibility / pro-forma agent, this number is load-bearing and, today, costs weeks of manual digging across municipal ordinances, utility fee schedules and county portals. We do the aggregation so your agent doesn't have to.

// add to your MCP client config
{ "mcpServers": { "muni-dev-cost": { "command": "npx", "args": ["-y", "muni-dev-cost-mcp"] } } }

Tools

1 free + 13 premium tools. The free get_dev_costs is the hook; the 13 premium tools are the depth a feasibility agent can't assemble itself.

Example (free)

POST https://muni-dev-cost-mcp.vercel.app/dev-costs
{ "jurisdiction": "Phoenix, AZ" }

🏗️  Phoenix, AZ  ·  coverage 🟢 deep
   Municipal development cost, single-family home: $29,322
     • Water + sewer (impact + tap): $29,322
   Fees included (one line each):
     • Wastewater Collection impact fee: $5,127  (per dwelling)
     • Wastewater Treatment impact fee: $3,753  (per dwelling)
     • Water Transmission impact fee: $14,046  (per dwelling)
     • Water Treatment impact fee: $4,387  (per dwelling)
     • Water Resource Acquisition fee: $2,009  (per dwelling)

Related MCP server: LandlordLaw MCP Server

Coverage (honest — regla 7)

We never pass off an estimate as a city's published number.

• 🟢 deep — the city's own water/sewer fee schedule was ingested, including the per-meter table. Figures are published.

• 🟡 partial — headline impact figures from public schedules; some categories estimated.

• 🟠 estimated — the exact city isn't in our deep KB yet, so figures are a regional benchmark, clearly marked. Use as order-of-magnitude only.

Coverage today: 130 jurisdictions across 38 states — 109 deep (own per-meter/per-LUE schedule ingested) + 21 partial. Dense in the high-growth markets a feasibility agent actually screens: TX (18), CO (18), FL (18), NC (16), CA (11), plus AZ, GA, WA, OR and more. From the cheapest covered market (Mobile, AL ~$1,000) to the priciest (Erie, CO ~$78,350), ranked and queryable. Any US city not yet ingested returns an honest state benchmark estimate — and the deep KB grows every iteration.

All fee data is sourced from public, government-published fee schedules (works of US municipal government → public domain). Each jurisdiction carries its source URL and effective date. Indicative — verify the exact amount with the jurisdiction. Not legal or fee-certification advice.

Two ways to pay for the premium tools

• 💳 Card (Stripe) — buy a prepaid API key at /pro/checkout, then set "env": { "MUNI_DEV_COST_KEY": "<key>" }.

• 🪙 x402 (USDC on Base) — AI agents pay per call automatically; no signup.

The free get_dev_costs works with no key.

How it stays a moat

The aggregation engine, the normalized fee knowledge base and the accumulating per-jurisdiction cache run server-side. The npm package is a thin client: it forwards your call to the hosted server and renders the response. The fee data and the premium logic never ship in the tarball — a moat verified on every build by npm run test:moat.

License

MIT. Source: https://github.com/Baneado98/muni-dev-cost