PatchOps

Available tools

26 tools

Tool	Description
`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.

About

Live queries against the Oklahoma Corporation Commission's public data, with no auth and 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 and 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. The other 2 are generic: 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 methods. 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.

Requirements

No authentication required
Free public OCC ArcGIS REST data, no access key needed

Setup

A few steps to connect your AI agents to Oklahoma Corporation Commission.

Get started

1
No Setup Required
This is a free public data connector with no authentication.
2
Start Querying
Search Oklahoma wells, pull recent drilling permits, or render any of the 49 OCC layers on the map.

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 Oklahoma Corporation Commission connector is ready to use in Claude.