PermitPal

Ohio SB 52 restricted areas

A read-only MCP connector over PermitPal's Ohio Senate Bill 52 dataset: restricted-area status relevant to utility-scale solar (50 MW or more) across all 1,308 Ohio townships in 88 counties, with the public sources behind each classification.

Scope is unincorporated territory. SB 52 restricted areas do not extend into incorporated municipalities, which is why cities and villages are not included. Built on the open MCP standard; works with Claude and ChatGPT.

Add it

Claude

In Claude desktop or web, open Settings → Connectors.
Click Add custom connector.
Enter:
- Name: for example, PermitPal Ohio SB 52
- Remote MCP server URL: https://ohiosb52mcp.permitpal.ai/mcp
- Authentication: none is required — this dataset is publicly accessible.
Click Add and allow Claude to scan the server's tools.
Start a new chat. The connector is available immediately; there is nothing to enable per conversation.

In Claude Code, one command does all of the above:

claude mcp add --transport http permitpal https://ohiosb52mcp.permitpal.ai/mcp

ChatGPT

In ChatGPT web, open Settings → Security and login.
Turn on Developer mode.
Open the Plugins tab from the left sidebar.
Click the + button.
Enter:
- Name: for example, PermitPal Ohio SB 52
- Connection > Server URL: https://ohiosb52mcp.permitpal.ai/mcp
- Authentication: choose No Auth — this dataset is publicly accessible.
Mark: I understand and want to continue.
Create it and allow ChatGPT to scan the server's tools.
Open a new chat, select PermitPal Ohio SB 52 from the tools menu, and start using it.

The connector is read-only and needs no API key. Everything below arrives with it — there is nothing else to install.

What you can ask it

Statewide picture — counts and estimated acreage for each status across all 1,308 townships. "What does the Ohio SB 52 landscape look like?"
County ranking — every county, or the top ten, by acreage under a confirmed no-restriction finding. "Which Ohio counties should we focus on?"
A single township — its status and the public sources behind it, with links. "What's the status of Liberty Township, Licking County?"
A specific site — status by coordinates, for a parcel or substation. "Is 41.517784, -82.993703 in a restricted area?"
Maps — a labelled choropleth, statewide or per county, ready to drop into a report. "Show me a map of Licking County."
Township polygons — one county at a time as GeoJSON, for QGIS or a web map. "Export the restricted townships in Logan County."
A market deck — a ranked county table, labelled maps, named townships with links to the county resolutions behind each classification, and a sourced footer on every slide. "Build me a deck on the Ohio solar market for our investment committee, using the @PermitPal connector."

The three statuses

SB 52 Restriction
An adopted restricted area applies somewhere in the township.
No SB 52 Restriction
Records establish that no adopted restricted area applies.
No Restriction Identified
The public record identified no indication that a restricted area exists. Confirm current status with the county.

Every township was researched, and the connector is built so no response can merge these three.

What this does not decide

Status reflects SB 52 restricted areas only. Siting also depends on Local Regulation and Development Codes, Community Sentiment, Decision Makers, and Project History. For a site-specific assessment across all of these, request a Project Intelligence report.

Use of your data

Every call records the tool name, the parameters you sent — including any coordinates, timing, status, and a caller identifier derived by hashing your network address with a secret we hold. That identifier is a pseudonym: stable enough to count users and detect misuse, and not reversible to an address by anyone who obtains the logs.

We do not receive your conversation with the assistant, your prompts, your name, or any account identifier. No account is needed to use this connector. Full detail is in permitpal.ai/privacy.

Terms of use

This connector is an invite-only evaluation service. Access is granted to an approved organisation to evaluate the data; it is not a free tier and it is not public. A URL is a means of access, not a grant of licence — please do not forward it outside your organisation.

Use the data for internal purposes: site screening, due diligence, internal analysis, internal maps and reports. Putting outputs into client deliverables or anything shared with a third party needs a paid licence — get in touch. Keep the attribution Source: PermitPal (permitpal.ai), which every response carries.

Do not redistribute the underlying data, use it to build a competing dataset, or issue repeated calls to assemble a larger extract than one response returns. Full terms at permitpal.ai/terms.