muni-dev-cost
# 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.
```jsonc
// add to your MCP client config
{ "mcpServers": { "muni-dev-cost": { "command": "npx", "args": ["-y", "muni-dev-cost-mcp"] } } }
```
## Tools
| Tool | Tier | What you get |
|---|---|---|
| `get_dev_costs` | **Free** | The aggregated municipal development cost for a jurisdiction (single-family home), split into water+sewer vs other impact, with a per-fee summary and an honest coverage label. |
| `get_fee_breakdown` | Premium | Every fee line by line, grouped (Water / Sewer / Transportation / Parks / Drainage), with the **per-meter-size schedule** and each source + effective date. |
| `compare_jurisdictions` | Premium | Rank 2β12 markets side by side for **site selection** β total, water+sewer split, the dollar/% spread and what it costs on a 100-unit project. |
| `get_water_sewer_detail` | Premium | Water & sewer connection cost **by meter size** (5/8" β 12") β the single biggest swing in a utility connection budget. |
| `estimate_dev_cost` | Premium | Whole-project fees (fees Γ units) with per-unit and extended line items, dev-type aware, explicit about exclusions. |
| `list_jurisdictions` | Premium | The full **coverage map** β every jurisdiction, its depth and data freshness, which publish a per-meter schedule, plus the benchmark states. |
| `get_fee_schedule_source` | Premium | The published **source document + per-fee provenance** (published vs estimated) behind a jurisdiction's number β defensible *trazabilidad* for a pro-forma. |
| `get_cost_trend` | Premium | The **real dated revision history** of a jurisdiction's headline fee (prior years + adopted future steps) with YoY delta and CAGR β never a projection. |
| `compare_by_meter_size` | Premium | One jurisdiction's water/sewer cost across **every published meter size**, ratioed to the 5/8" residential base. |
| `estimate_by_units` | Premium | **Multifamily/mixed** fee estimate by LUE (units Γ LUE-per-unit) β the way cities actually bill MF, so it doesn't overstate fees. |
| `get_total_dev_cost` | Premium | The **grand total across every fee category** (water/sewer, transportation, parks, drainage, public-safety, other), bucketed β with honest $0 buckets where a city simply doesn't charge that category. |
| `breakdown_by_fee_category` | Premium | Every line item within **one** category (e.g. all of a city's parks fees) with per-meter detail β errors honestly if the city doesn't levy that category. |
| `rank_jurisdictions_by_cost` | Premium | Rank the **entire covered KB** cheapestβpriciest by water+sewer or total, with cheapest/median/priciest, the spread, and a site-selection insight β filterable by state/coverage. |
| `summarize_by_state` | Premium | A **state-level roll-up** over the whole KB: per state, the city count, min/median/max cost, cheapest/priciest city, and which fee categories are assessed β the map for "which states are cheap/expensive to build in." |
> **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)
```
## 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
TDQS
Scored across 14 tools
Each tool targets a distinct aspect of municipal development cost data: basic cost, fee breakdown, water/sewer detail, comparisons, rankings, estimates, trends, and coverage listing. No two tools have overlapping purposes; even similar tools like get_dev_costs and get_total_dev_cost are clearly differentiated by scope (single-family vs grand total across categories).
All tool names follow a consistent verb_noun pattern in snake_case, e.g., get_dev_costs, compare_jurisdictions, list_jurisdictions, rank_jurisdictions_by_cost. Variants like breakdown_by_fee_category and estimate_by_units maintain the pattern with 'by_' prepositions. No mixing of styles or vague verbs.
With 14 tools, the set is well-scoped for a municipal development cost data service. It covers basic queries, detailed breakdowns, comparisons, rankings, estimates, trends, and coverage metadataβeach tool earns its place without being overwhelming or too sparse.
The tool surface comprehensively covers the domain: basic single-family cost (get_dev_costs), total cost across all fee categories (get_total_dev_cost), fee-by-fee breakdown (get_fee_breakdown), water/sewer detail per meter size (get_water_sewer_detail), category-specific breakdown (breakdown_by_fee_category), multi-jurisdiction comparison (compare_jurisdictions), national ranking (rank_jurisdictions_by_cost), state-level summary (summarize_by_state), cost trends (get_cost_trend), fee schedule provenance (get_fee_schedule_source), project estimates (estimate_dev_cost, estimate_by_units), and coverage listing (list_jurisdictions). No obvious gaps exist for a read-only query service.