UT Division of Oil, Gas and Mining

Live

Utah DOGM — UT O&G regulator. ~40K surface wells with operator + cumulative production, ~33K bottomhole locations (deviated wells), ~12.5K directional well-path polylines. Uinta Basin operator side (Crescent Energy / Ovintiv / KODA Resources) + Greater Aneth.

What is UT Division of Oil, Gas and Mining?

Utah Division of Oil, Gas and Mining (UT DOGM) — UT O&G regulator. Probed 2026-05-02. AGOL services.arcgis.com/ZzrwjTRez6FJiOq4 owned by OGMGIS_utahDNR. 3 services via 5 methods: searchWells (~39,997 surface wells with rich attribution — Operator/County/WellStatus/WellType/cumulative production/PLSS) ⭐, searchBottomHoles (~32,989 bottom-hole locations — deviated wells, ConstructType Vertical/Directional/Horizontal) ⭐, searchWellPaths (~12,541 directional drilling polylines), getWellByApi single-well lookup, getServiceInfo. **upstream quirks**: Surface County is UPPERCASE STRING ('DUCHESNE','UINTAH','SAN JUAN'); BottomHole County is INTEGER code (Duchesne=7, Uintah=24, San Juan=19, Salt Lake=18, Box Elder=2 etc.) — handler translates from county name input via DOGM_COUNTY_CODES. WellStatus 15 distinct codes (P=Producing 12182, PA=Plugged 10014, LA=Located Abandoned 10636, APD=Approved Permit 1772, A=Active 1595, S=Shut-in 2021); WellType 20 codes (OW=Oil Well 16748, GW=Gas Well 16153, D=Dry 4347, WI=Water Inj 2104). Well Paths layer has only API + ConstructStatus + Shape__Length — no operator/county/wellName; join via API back to surface wells. **Spec drift**: searchPermits dropped — UT DOGM does NOT publish O&G permits as a Feature Service. The `Minerals_Permits_View_Layer` (1,504 records) is for MINING permits only (sand/gravel/coal). APD-status surface wells (1,772 records) is the closest substitute via searchWells({wellStatus:'APD'}). Surface lat/lon stored as both Latitude/Longitude doubles AND geometry.x/y.

Available Tools

searchWells
UT surface wells (~40K). Filter operator/county/wellStatus/wellType/bbox/near. County UPPERCASE.
getWellByApi
Single-well lookup by 10-digit API. Returns the surface-well record.
searchBottomHoles
UT bottomhole locations (~33K). Filter constructType/county/deviatedOnly. County is INTEGER code; handler translates.
searchWellPaths
UT directional well-path polylines (~12.5K). Filter api/constructStatus/bbox/near. No county/operator.
getServiceInfo
Schema + record counts for any of 3 services. Pass `service` to scope.

Requirements

ENABLE_ENERGY_APIS
Set ENABLE_ENERGY_APIS=true to allow connector toggles.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Set ENABLE_ENERGY_APIS=true for your deployment.

Open /mcp and turn on UT Division of Oil, Gas and Mining with the energy switch.

Call the ut-dogm MCP tool — start with method=searchWells or method=searchBottomHoles.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect UT Division of Oil, Gas and Mining 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 UT Division of Oil, Gas and Mining 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 UT Division of Oil, Gas and Mining 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:

"UT Division of Oil, Gas and Mining-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"
}