ND Department of Environmental Quality

Live

North Dakota DEQ environmental data — Bakken-era oil/brine spill mirror, well-pad stormwater permits by operator, groundwater monitoring, 303(d) impaired streams. Major spec drift caught at probe.

What is ND Department of Environmental Quality?

North Dakota Department of Environmental Quality (ND DEQ) public ArcGIS surface + 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 AGOL — methods reframed against the agency's actual published layers plus the long-cited FracTracker spill mirror (third-party, ~5,367 records, 2014-era extract — 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 — county filter silently ignored, use bbox/near. Brine + 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`).

Available Tools

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.

Requirements

ENABLE_ENVIRONMENTAL_APIS
Set ENABLE_ENVIRONMENTAL_APIS=true to allow connector toggles.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Set ENABLE_ENVIRONMENTAL_APIS=true for your deployment.

Open /mcp and turn on ND DEQ with the environmental switch.

Call the nd-deq MCP tool — start with method=searchSpills or method=searchStormwaterPermits.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect ND Department of Environmental Quality to Claude:

Step 1: Open Claude Settings

Launch Claude → Click the profile button (bottom left) → Navigate to Settings

Step 2: Access Connectors

Scroll down to the Connectors tab → Navigate to the bottom → Click “Add Custom Connector”

Step 3: Name Your Connector

Enter any name you'd like for this connector

Step 4: Get the Connector URL

Step 5: Add the Connector

Paste the URL in the “Remote MCP Server URL” text box → Click Add

Step 6: Start Using

Your connector is now ready to use in Claude

Follow these steps to connect ND Department of Environmental Quality to ChatGPT:

Step 1: Enable Developer Mode

Go to Settings → Connectors → Advanced → Enable Developer mode

Step 2: Create New Connector

Go back to Connectors page → Click “Create” (top right)

Step 3: Name Your Connector

Enter any name you'd like for this connector (descriptions are optional)

Step 4: Get the Connector URL

Step 5: Add the URL

Paste the URL in the “MCP Server URL” text box

Step 6: Set Authentication

Click the authentication dropdown → Select “No authentication” (PatchOps handles authentication internally)

Step 7: Create the Connector

Click “I understand and want to continue” checkbox → Press Create

Step 8: Using the Connector

Start a new chat → Click the + button (left of text box) → Open dropdown → Hover over three dots labeled “More” → Select your connector

Instructions for connecting ND Department of Environmental Quality to GitHub Copilot:

Coming Soon

Detailed setup instructions for GitHub Copilot will be added here.

For other MCP-compatible platforms:

Step 1: Get the Connector URL

Step 2: Add to Configuration

Add this configuration to your MCP settings file. Replace the URL with your specific connector URL from the /mcp page:

"ND Department of Environmental Quality-MCP": {
  "url": "https://patchops.ai/api/mcp/...",
  "type": "http"
}

Example Configuration

Here’s an example using PatchOps MCP:

"PatchOps-MCP": {
  "url": "https://patchops.ai/api/mcp/...",
  "type": "http"
}