Back to MCP Servers
Oklahoma Corporation Commission logo

Oklahoma Corporation Commission

Live

Oklahoma's regulator-of-record for oil & gas — 49 live ArcGIS layers covering wells, permits, completions, UIC, units, seismicity, hydrology, and more. No auth, no ETL.

What is Oklahoma Corporation Commission?

Live queries against the Oklahoma Corporation Commission's public ArcGIS REST — no auth, no ETL. 26 methods total: 24 named convenience methods cover the high-value layers — wells (RBDMS, orphan, state-funds, well logs), completions, horizontal laterals, UIC wells (with commercial-only flag), permits (Intent-to-Drill), drilling/spacing units, field rules, surface facilities, oil & gas incidents, gas storage, PST tanks/releases, induced-seismicity zones (AOI / reduction areas / HF AOI), hydrology (rivers/streams/lakes/aquifers), base-of-treatable-water, public water supply, groundwater wells, sedimentary basins, PLSS cadastral, and OCC districts. Plus 2 generic methods: queryLayer({ layer, where, bbox, ... }) exposes every layer in the catalog and listLayers() returns the key list — together they cover the long tail (risk overlays, recycling pits, ECRS incidents, federal land, etc.) without needing 50 hand-tuned wrappers. Each method returns features plus a ready-to-render GeoJSON FeatureCollection that plugs straight into the persistent map. Production volumes are NOT at OCC — those live with the Oklahoma Tax Commission and are out of scope.

Available Tools

  • searchWells
    Search OCC RBDMS wells statewide. Filter by API, operator, county, well_status (ACTIVE/PLUGGED auto-aliased to short codes), well_type, bbox, or proximity.
  • getOrphanWells
    Orphan-funds wells — abandoned wells eligible for state plugging.
  • getStateFundsWells
    State-funds wells (RBDMS state plugging program).
  • getWellLogs
    RBDMS well-log records linked to wells.
  • getCompletions
    Well completion records (COMP_WELLS).
  • getHorizontalLaterals
    Horizontal-lateral wellbore polylines (HF_LATERALS).
  • getUICWells
    Class II disposal/injection wells. Pass commercial_only=true for third-party commercial disposal sites.
  • getPermits
    OCC Intent-to-Drill (ITD) drilling permits — analog of the RRC drilling permit master.
  • getDrillingUnits
    Drilling/spacing-unit polygons. Pass active=false for inactive units.
  • getFieldRules
    Field-rule polygons. Pass municipal=true for city/town overrides.
  • getFacilities
    Surface facilities (production sites, tank batteries).
  • getOilGasIncidents
    Oil & gas incident records — releases, spills, blowouts reported to OGCD.
  • getGasStorage
    Underground gas-storage unit polygons.
  • getPSTTanks
    Registered petroleum storage tanks.
  • getPSTReleases
    PST release sites — confirmed contamination events.
  • getInducedSeismicity
    ISD regulatory zones. Pass zone: 'aoi' (default), 'central_reduction', 'western_reduction', 'geo_provinces', or 'hf_aoi'.
  • getHydrology
    Hydrography features. Pass layer: 'rivers', 'streams', 'lakes' (default), or 'aquifers'.
  • getBaseTreatableWater
    Base-of-treatable-water control points. Pass contour=true for the depth-contour line layer.
  • getPublicWaterSupplyWells
    DEQ Public Water Supply wells.
  • getPublicWaterSupplyIntakes
    DEQ Public Water Supply surface intakes.
  • getGroundwaterWells
    OWRB groundwater wells (water-rights monitoring).
  • getSedimentaryBasins
    Sedimentary basins polygons.
  • getCadastral
    PLSS polygons. Pass layer: 'sections' (default), 'townships', or 'counties'.
  • getDistricts
    OCC field-office district polygons.
  • queryLayer
    Generic query against any layer in the OCC catalog. Pass layer (key from listLayers), where (raw SQL), equals, like, bbox, proximity. Use for long-tail layers (whpa, high_risk_areas, lost_circulation, ECRS incidents, recycling pits, federal land, etc.).
  • listLayers
    Return the OCC layer catalog (49 layers) — call this to discover which keys queryLayer accepts.

Requirements

  • No authentication required
    Free public OCC ArcGIS REST data — no API key needed

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

This is a free public data connector with no authentication.

Search Oklahoma wells, pull recent drilling permits, or render any of the 49 OCC layers on the map.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect Oklahoma Corporation Commission 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

Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use

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 Oklahoma Corporation Commission 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

Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use

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 Oklahoma Corporation Commission 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

Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use

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:

"Oklahoma Corporation Commission-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"
}