PatchOps

Available tools

5 tools

Tool	Description
`searchSpillsAndReleases`	Ohio EPA spills + releases (~16K, since May 2017). Filter county/product/district/yearFrom/yearTo/cityTown.
`searchBrownfields`	DERR Targeted Brownfield Assessment grants (~217). NO county column, bbox/near only. Filter project/applicant/fiscalYear.
`searchNPDESPermits`	Active individual NPDES permits (~3.1K). Filter county/facility/permitType (Industrial/Public)/district.
`getEPADistrict`	Point-in-polygon: which OEPA district contains a lat/lon? Returns districtCode + districtName + polygon.
`getServiceInfo`	Schema + record counts for any of the 4 services.

About

Ohio EPA environmental compliance connector. Probed 2026-05-02. Spec drift: the scoping doc warned that a public-data search via owner `portaladmin11` returned 262 hits but many were third-party, so filter strictly to authoritative Ohio EPA-published data. The probe found the agency native server at `agency data services/` with 19 thematic folders. All 4 layers used here are agency-native, not third-party public-data mirrors. Layers: EmergResponse/Spills2_Public/1 'Spill Sites and Products' (~16,157, a broad spills-plus-products view; layer 0 is sites-only and narrower, so the handler uses layer 1 because it links spill product details), Derr/TBA_Sites_Public/0 (~217 DERR Targeted Brownfield Assessment grant sites, from the Division of Environmental Response & Revitalization), SurfaceWater/NPDES/0 'Individual Permits' (~3,148 active: Industrial=1,032, Public=2,116; permit_status always 'ACTIVE'; district distinct NEDO=1,124, NWDO=711, SEDO=516, SWDO=495, CDO=294, OUTS=8), and geopol/Boundaries_WM/2 'OEPA Districts WM' (5 polygons: CDO/NEDO/NWDO/SEDO/SWDO with one ESW outlier in the spills data). Upstream quirks (probed): the Spills2_Public layer 1 `county` column is Title Case with trailing whitespace ('Tuscarawas ', 'Belmont '), so the handler uses LIKE 'X%'. `reportedproduct` is similarly space-padded to ~75 chars (the handler trims output). `oepadist` has 7 distinct values: SEDO=1928, CDO=2310, NEDO=4499, SWDO=3019, NWDO=3680, ESW =5, NULL=716 (some with trailing whitespace, some a literal 'NULL' string, which the handler normalizes). NPDES `county` is Title Case 'Belmont' with no trailing whitespace, unlike Spills. All 3 native data services use a lowercase `objectid` as the OID, different from most data services. The Brownfields layer has no county column, so the county filter works only on Spills and NPDES; Brownfields uses bbox/near for spatial scoping. getEPADistrict is a point-in-polygon query against geopol/Boundaries_WM/2. maxRecordCount: spills=2000, brownfields=2000, npdes=4000, districts=1000.

Requirements

ENABLE_ENVIRONMENTAL_APIS
Set ENABLE_ENVIRONMENTAL_APIS=true to allow connector toggles.

Setup

A few steps to connect your AI agents to Ohio EPA.

Get started

1
Enable Environmental APIs
Set ENABLE_ENVIRONMENTAL_APIS=true for your deployment.
2
Toggle Connector On
Open /mcp and turn on Ohio EPA with the environmental switch.
3
Start Querying
Call the oh-epa MCP tool, start with method=searchSpillsAndReleases or method=searchBrownfields.

Connect to your AI assistant

Pick the tool your team uses for the exact setup steps.

1
Open Claude settings
Launch Claude, click the profile button (bottom left), and go to Settings.
2
Access connectors
Open the Connectors tab, scroll to the bottom, and click “Add custom connector”.
3
Name your connector
Enter any name you’d like for this connector.
4
Get the connector URL
Log in to PatchOps, open the /mcp page, and copy the connector URL you want to use.
5
Add the connector
Paste the URL into the “Remote MCP server URL” box and click Add.
6
Start using
Your Ohio EPA connector is ready to use in Claude.