PatchOps

Available tools

5 tools

Tool	Description
`searchSpills`	Bakken oil + brine spills (FracTracker, 2014). Filter county/operator/date/spillType.
`searchStormwaterPermits`	Construction Stormwater permits (~2.9K). Filter permittee/site/permit prefix.
`searchGroundwaterMonitoring`	Aquifer monitoring polys (~278). Filter name/program/bbox/near.
`searchImpairedStreams`	Assessed reaches (~34.8K). category:'impaired' for 303(d) Cat 5/5A.
`getServiceInfo`	Schema + record counts for any of the 5 services.

About

North Dakota Department of Environmental Quality (ND DEQ) public data surface plus FracTracker mirror. **Major spec drift caught at probe**: ND DEQ does NOT publish spills, USTs, air permits, or abandoned brine pits as Feature Services on public data. Methods are reframed against the agency's actual published layers plus the long-cited FracTracker spill mirror (third-party, ~5,367 records, 2014-era extract, the only programmatic ND O&G spill source). What ND DEQ DOES publish: ~2,950 Construction Stormwater permits (~2,944 Active), operator name searchable (`envintName`), Bakken well-pad construction permits visible (Burlington Resources, Continental Resources, Hess, etc.); ~278 Groundwater Monitoring polygons (Agricultural / Western / Not Sampled); ~34,849 assessed stream reaches with 303(d) Category labels (Cat 5/5A = TMDL needed/underway, Cat 4A = TMDL complete); plus lakes/BMPs/319-projects ancillary. Stormwater layer has NO COUNTY column, so the county filter is silently ignored; use bbox/near. Brine and crude oil spill services share the same upstream dataset; handler dedupes by Incident_ID when spillType:'all'. Field naming is mixed-case across layers (camelCase `envintName`/`swsStatus`, ALL CAPS `NAME`/`Program`/`CATEGORY`).

Requirements

ENABLE_ENVIRONMENTAL_APIS
Set ENABLE_ENVIRONMENTAL_APIS=true to allow connector toggles.

Setup

A few steps to connect your AI agents to ND Department of Environmental Quality.

Get started

1
Enable Environmental APIs
Set ENABLE_ENVIRONMENTAL_APIS=true for your deployment.
2
Toggle Connector On
Open /mcp and turn on ND DEQ with the environmental switch.
3
Start Querying
Call the nd-deq MCP tool, start with method=searchSpills or method=searchStormwaterPermits.

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 ND Department of Environmental Quality connector is ready to use in Claude.