ND Industrial Commission DMR

Live

North Dakota Department of Mineral Resources — Bakken/Three Forks oil & gas operator data. ~25.5K wells, ~15.8K horizontal legs, drilling/completion permits, FracTracker spill mirror.

What is ND Industrial Commission DMR?

North Dakota Industrial Commission Department of Mineral Resources (NDIC DMR) public oil & gas data. The native dmr.nd.gov fee services are paywalled (HTTP 401); the AGOL `sbogan_worldmap` mirror exposes the public extracts. ~25,539 wells with 14-digit hyphenated `api_no`, full PLSS (`twp`/`rng`/`sec`/`qq`) queryable, status enum (A=8,973 / PA=3,786 / DRY=6,163 / Confidential=2,039 in 6-month tight-hole window / DRL=356 / LOC=342 / IA=572 / TA=354), well-type enum (OG=21,410 / SWD=648 / WI=766 / GASD/GASC/GASN). County stored UPPERCASE — handler queries with `UPPER(County)='X'` and Title-Cases on output. ~15,861 horizontal-leg polylines (sparse upstream, only `linekey` = `<api>_LATn`). Companion `ND_Wells` layer carries cumulative `TotalOil`/`TotalWater`/`TotalGas` aggregates; `searchProductionByField` joins by FileNo. Spills come from the FracTracker `NDBrineSpills` + `NorthDakotaCrudeOilSpills` mirror (~5,367 records each — same upstream dataset, 2014-era extract). McKenzie / Williams / Mountrail counties dominate the Bakken core.

Available Tools

searchWells
ND O&G wells (~25.5K). Filter county/operator/status/well_type/twp/rng/sec/bbox.
searchPermits
Drilling/completion permits — wells in LOC/DRL/PNC/EXP/PNS states.
getWellByApi
Single well lookup by 14-digit API (hyphenated or unhyphenated).
searchHorizontalLegs
Bakken horizontal legs (~15.8K). Filter api/bbox/near/minLengthFt.
searchProductionByField
Aggregate cumulative oil/gas/water for wells in a named field.
searchSpills
Bakken-era oil + brine spill mirror (FracTracker, 2014-era).
getServiceInfo
Schema + record counts for any of the 5 services.

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 ND DMR with the energy switch.

Call the nd-dmr MCP tool — start with method=searchWells or method=searchPermits.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect ND Industrial Commission DMR 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 ND Industrial Commission DMR 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 ND Industrial Commission DMR 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:

"ND Industrial Commission DMR-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"
}