What is AR Oil & Gas Commission?
Arkansas Oil & Gas Commission well registry mirrored by the Arkansas State GIS Office at agency data services. Three curated layers: layer 5 OIL_AND_GAS_WELLS_AOGC (~38,245 wells with rich AOGC schema — permitnumberstring, wellid, operatorname, wellname, welltype, welltypedescription, wellstatus, wellstatusdescription, countyname, poolnamestring, fieldname, section/township/range, depthbottom); /8 PIPELINES_USGS_1986 (~719 historical polylines — USGS 1986 snapshot, NOT live AOGC data); /20 LITHIUM_LEASED_AREAS_AOGC (~7 Smackover-Norphlet brine polygons — Standard Lithium + ExxonMobil commercial-scale acreage). Top counties: UNION 7,112 (19% — South AR Smackover oil); FRANKLIN 3,116 / SEBASTIAN 2,469 / LOGAN 2,095 (Arkoma); OUACHITA 2,855 / COLUMBIA 2,839 / LAFAYETTE 2,371 (Smackover); VAN BUREN 1,846 / CONWAY 1,480 (Fayetteville Shale). Top welltype: GAS 19,082 (50%), OIL 16,793 (44%), SWD 1,282, EOR 328, EXP 283, CBM 71, GS 33. Top wellstatus: PR 16,570, PA 16,061, A 3,385, EX 1,232, TA 304, AOW 267, IN 255. §0 spec drift caught: build-plan said Location/data services for wells — that has only GNIS-style geographic names, NO O&G; Utilities/data services doesn't exist (only PrintingTools/RasterUtilities/Symbols sub-services). Canonical wells live at layer 5. Field names lowercase upstream (operatorname, wellstatus); CountyName stored UPPERCASE. wellstatus has lowercase 'ex' typo alongside canonical 'EX'. ; Last verified live 2026-05-07.
Available Tools
Requirements
- Toggle onToggle on and use — no setup needed.
Quick Setup Guide
Follow these steps to connect your AI agents to this connector
Open /mcp and enable AR Oil & Gas Commission with the toggle — no credentials needed.
Call searchWells with county: 'VAN BUREN' and wellType: 'GAS' for Fayetteville Shale, or searchLithiumLeasedAreas to see commercial-scale Smackover brine acreage.
Connect to Your AI Assistant
Choose your AI assistant below for specific setup instructions
Follow these steps to connect AR Oil & Gas 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 AR Oil & Gas 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 AR Oil & Gas 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:
"AR Oil & Gas 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"
}