ND Department of Trust Lands

Live

North Dakota state-trust mineral and surface leases. ~33K mineral tracts (8.9K active O&G leases) + ~4.9K surface (grazing/ag) tracts. Bakken-relevant acquisition signal feed.

What is ND Department of Trust Lands?

North Dakota Department of Trust Lands (NDDTL) AGOL Feature Services covering state-trust mineral and surface land tracts. ~33,273 mineral tracts (8,911 Leased / 24,348 Available / 14 Not Available) — oil & gas leases identified by `OG-YYYY-NNNNN` lease prefix in the composite `lease` descriptor (e.g. `Golden Valley - 138-104-36-NE4 - OG-2025-13594`). NDDTL does not publish OG-leases as a separate layer; handler filters with `UPPER(lease) LIKE '%OG-%'` plus `eligible='Leased'`. ~4,888 surface tracts (mostly grazing/ag — `AG-` prefix; LESSEE field heavy on grazing associations). Two surface-layer variants: a thin view and the richer Trust_Land_Surface (LESSEE / ANNUAL_RENT / PUBLIC_ACCESS / LEASE_EXPIRATION as epoch-ms). `effective`/`exp` on minerals view stored as MM/DD/YYYY string (with single-space ' ' for null) — handler normalizes to ISO. Counties stored Title-Case (different from ND DMR's UPPERCASE). Top operators: Continental Resources, Phoenix Energy One, Petro-Sentinel, Kraken, OKreek, XTO, Topaz Energy. landtrustdash.nd.gov referenced in spec is offline; AGOL views are the working public surface. McKenzie / Mountrail / Williams counties dominate active OG-leases.

Available Tools

searchOilGasLeases
ND state-trust O&G mineral leases. Filter county/lessee/eligible/twp/rng.
searchSurfaceLeases
ND state-trust surface/grazing leases. Pass rich:true for ANNUAL_RENT.
getLeaseDetail
Single lease lookup by number across mineral + surface views.
getExpiringLeases
Leases expiring within windowDays (default 365). Acquisition signal.
getServiceInfo
Schema + record counts for any of the 3 layers.

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 Trust Lands with the energy switch.

Call the nd-lands MCP tool — start with method=searchOilGasLeases or method=getExpiringLeases.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect ND Department of Trust Lands 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 Department of Trust Lands 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 Department of Trust Lands 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 Department of Trust Lands-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"
}