OK DEQ Oklahoma Environmental

Live

Oklahoma DEQ wellhead protection, remediation, and monitoring — drilling-restriction WHPA polygons, institutional-controls cleanups, voluntary cleanup sites, accredited labs, and air-quality monitoring.

What is OK DEQ Oklahoma Environmental?

Oklahoma Department of Environmental Quality (OK DEQ) native ArcGIS REST MapServers at gis.deq.ok.gov. ~5,911 Wellhead Protection Area (WHPA) polygons — drilling-restriction overlays around public water supplies, ZONE A (innermost) / B / C (outermost) — no name or county upstream, just SOURCE_IND. ~890 Remediation Institutional Controls under formal cleanup programs (Brownfields, RCRA, SCAP, Superfund, VCP, Solid Waste). Voluntary Cleanup Program site list. ~151 state-accredited labs (Lab_Type: Commercial, Field, Industrial, Municipal, Permittee — with upstream typos like Muncipality vs Municipal). 28 air-quality monitoring sites tracking O3, PM2.5, NO2, SO2, CO, Hg, Lead, and Toxics. Counties returned in Title Case; handler strips trailing ' County' from upstream values like 'Tulsa County'.

Available Tools

searchWellheadProtectionAreas
WHPAs (~5.9K) — drilling-restriction polygons. Filter zone (A/B/C), bbox, near.
searchRemediationSites
Institutional Controls (~890). Filter county, program (Brownfields, RCRA, VCP, ...).
searchVoluntaryCleanupSites
Voluntary Cleanup Program sites — facility names + site IDs.
searchAccreditedLabs
State-accredited labs (~151). Filter by labType substring.
searchAirQualitySites
OK DEQ air monitoring (28 sites). Filter by county or pollutant substring.
getServiceInfo
Schema + record counts for any of the 5 OK DEQ 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 OK DEQ with the environmental switch.

Call the ok-deq MCP tool — start with method=searchWellheadProtectionAreas.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect OK DEQ Oklahoma Environmental 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 OK DEQ Oklahoma Environmental 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 OK DEQ Oklahoma Environmental 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:

"OK DEQ Oklahoma Environmental-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"
}