US Building Permit Aggregator
RemoteAbout US Building Permit Aggregator
US Building Permit Aggregator collects recent building permits from nine US cities in a unified schema. It is intended for construction lead generation, market research, and real-estate analysis, using government open-data portals and nulls for unavailable fields.
Key features
- 01Collect permits from nine US cities
- 02Normalize data from different portals
- 03Filter by jurisdiction and issue date
- 04Set a per-jurisdiction record limit
- 05Return fields such as contractor, valuation, and address
Use cases
- 01Find leads from newly permitted projects
- 02Compare activity by city, contractor, or work type
- 03Research neighborhood development and renovation
- 04Identify active contractors and owners by area
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregatorclaude mcp add --transport http dizzyvinci-building-permit-aggregator https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator{"mcpServers":{"dizzyvinci-building-permit-aggregator":{"type":"http","url":"https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"}}}Open in Cursor{"servers":{"dizzyvinci-building-permit-aggregator":{"type":"http","url":"https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"}}}Open in VS Code{"mcpServers":{"dizzyvinci-building-permit-aggregator":{"type":"http","url":"https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"}}}{"mcpServers":{"dizzyvinci-building-permit-aggregator":{"serverUrl":"https://mcp.apify.com?tools=dizzyvinci/building-permit-aggregator"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEUS Building Permit Aggregator — Multi-City Construction Leads
Pull recent building & construction permits from 9 major US cities in one clean, unified schema — straight from official open-data portals. One run, one format, every city.
Who uses this
- Construction lead generation — find newly permitted projects (roofing, HVAC, solar, remodels) before competitors; sell to suppliers and subcontractors.
- Market & competitive intelligence — track construction valuation and volume by city, contractor, and work type.
- Real-estate & investment research — spot new development and renovation activity by neighborhood.
- Contractor prospecting — surface active contractors and project owners by area.
Coverage (v1)
Chicago, Los Angeles, Austin, San Francisco, Seattle, Washington DC, Nashville, Philadelphia, Boston — and growing. All data comes from public government open-data APIs (Socrata, ArcGIS, Carto, CKAN); no login or paywall.
Unified output schema
Every permit, regardless of source city, comes back as:
{
"jurisdiction": "Chicago", "state": "IL", "sourcePortal": "socrata",
"permitNumber": "100-XYZ", "permitType": "NEW CONSTRUCTION",
"workDescription": "New 3-story residential", "valuation": 250000,
"contractorName": "ACME BUILDERS", "ownerName": null,
"address": "123 N STATE ST", "city": "Chicago", "zip": null,
"latitude": 41.9, "longitude": -87.6,
"issueDate": "2025-05-01", "status": null,
"scrapedAt": "2026-06-02T12:00:00.000Z"
}
Fields a given city doesn't publish come back as null (e.g., some cities don't expose contractor or valuation).
Input
| Field | Type | Description |
|---|---|---|
jurisdictions | array | ["all"], or specific ids (e.g. ["chicago","nyc"]) |
sinceDays | integer | Only permits issued in the last N days (default 30; 0 = no date filter) |
maxRecordsPerJurisdiction | integer | Cap per city per run (default 1000) |
Notes
- Priced pay-per-event: you pay per permit returned. No subscription.
- Schedule it (e.g. daily,
sinceDays: 1) to build a fresh permit feed for your market.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.