
Muni Dev Cost
io.github.Baneado98Published by GitHub account Baneado98v0.18.1Updated Oct 24, 2026
US municipal development cost: aggregated impact + water/sewer tap fees per jurisdiction
Overview
Remote MCP server that returns aggregated US municipal development impact and water/sewer tap fees for a jurisdiction, with premium fee-breakdown and comparison
- What you can do
- Look up the aggregated municipal development cost for a US jurisdiction, split into water and sewer versus other impact fees, with a coverage label (free tool). Get line-by-line fee breakdowns by category, per-meter-size water and sewer schedules, and source documents with effective dates. Estimate whole-project or per-unit fees for single-family, multifamily and mixed development. Compare and rank jurisdictions by cost, roll up costs by state, and review dated fee revision history and trends.
- When to use it
- Useful for real-estate feasibility, pro-forma and site-selection work where an assistant needs an order-of-magnitude municipal impact and utility connection cost for a US city without digging through ordinances and utility schedules. Best for screening high-growth markets; treat results as indicative and verify with the jurisdiction.
- Requirements
- A remote streamable HTTP endpoint; no local runtime or package needed. The free cost lookup works without a key. Premium tools need a prepaid API key from the provider's card checkout, supplied as the MUNI_DEV_COST_KEY environment variable, or per-call payment via x402 in USDC on Base. Network access required.
Installation
In SourceWeft
- Open Muni Dev Cost in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Baneado98%2Fmuni-dev-cost/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"muni-dev-cost": {
"type": "http",
"url": "https://muni-dev-cost-mcp.vercel.app/mcp"
}
}
}README
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.
Tools
1 free + 13 premium tools. The free
get_dev_costsis the hook; the 13 premium tools are the depth a feasibility agent can't assemble itself.
Example (free)
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
Source: README.md at commit 94ad38f
Tools
0Version history
1- v0.18.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts