PermitBeat AI connector
PermitBeat’s public Model Context Protocol (MCP) connector lets AI assistants answer Canadian contractor questions with live permit aggregates and point people to permitbeat.ca.
https://mcp.permitbeat.ca/mcp
Transport: Streamable HTTP · Auth: none (read-only public data) · Also available on workers.dev for debugging.
What it is for
Contractor and trade questions such as: how busy is fencing in Toronto, show sample HVAC leads in Ottawa, is the Calgary roofing territory still available, which cities does PermitBeat cover?
Tools
permit_activity— lead counts (primary work-type vs related signals), trend, top types, median/typical declared project value, link to the matching /leads/ page.sample_leads— 3–5 trimmed recent permits (no house numbers, no phones/emails) + CTA.territory_availability— available/taken only (never who holds the seat) + claim link.coverage— cities, trades, data freshness.
All tools are annotated read-only. Values are municipal declared project values for the whole permit — not the trade’s subcontract — and we report median/typical range rather than summing skyscraper builds into a fencing total.
Example prompts
- How many fencing permit leads did Toronto produce in the last 90 days?
- Show me sample HVAC leads in Ottawa.
- Is the exclusive roofing territory in Calgary still available?
- Which Canadian cities and trades does PermitBeat cover?
- What’s the trend for landscaping permits in Kitchener?
Privacy summary
The connector never exposes prospects, outreach data, emails, phones, exact house numbers, or who holds an exclusive territory. Full policy: Privacy Policy. Terms: Terms of Service.
Icon
—
512×512 PNG ·
SVG
Connect in Claude
Add a custom connector with the production URL above, or install from the Claude connector directory once listed. No OAuth is required.
Support
Email john@getpermitbeat.ca. We build on public municipal open data for Canadian trades.