UT School & Institutional Trust Lands logo

UT School & Institutional Trust Lands

Live

Utah SITLA — ~3.4M acres of state trust lands, strongest state-trust portfolio per acre after TX. ~851 active O&G mineral leases (76 actively producing), ~5.5K historical/expired leases, ~16K surface land-ownership polygons (5,180 SITLA-administered).

What is UT School & Institutional Trust Lands?

Utah School and Institutional Trust Lands Administration (SITLA). Probed 2026-05-02. **TWO distinct origins**: gis.trustlands.utah.gov/mapping/rest/services owned by UtahSITLA for active + inactive Contracts; gis.trustlands.utah.gov/server/rest/services owned by plpcoadmin_agol for Ownership/LandOwnership_WM. 3 services via 5 methods: searchOilGasLeases (~851 active O&G + hydrocarbon contracts) ⭐ — note this is **layer 1 NOT layer 0** of Contracts_Oil_Gas (layer 0 is the 8-record 'Other Business Arrangements ML 90000+' admin holds for helium/hydrogen); searchInactiveLeases (~5,526 historical/expired) — separate Contracts_Oil_Gas_Inactive service; searchSurfaceOwnership (~15,968 polygons; owner Federal/Private/State/Tribal; agency BLM 3018/SITLA 5180/USFS 654/USFWS 33/DOD 37/NPS 77/UDOT 330/Tribal 190/Private 5658) ⭐; getLeaseDetail single-lease lookup by leasegis (e.g. 'ML22161.0'); getServiceInfo. **upstream quirks**: AGOL search results pointed at /server/rest/services/Contracts/UT_SITLA_Contracts_Active_OilGas/ but THAT URL returns 404 — authoritative live URL is at /mapping/rest/services/Contracts_Oil_Gas/ under owner UtahSITLA. class column has trailing spaces ('ML ', 'UO '). Active O&G dates are esriFieldTypeDate (epoch ms); inactive dates are esriFieldTypeString MM/DD/YYYY format — handler reconciles via dateFromAny(). Active layer has NO county column — bbox/near for spatial scoping (county filter is silently dropped, surfaced in notes). Ownership county column is lowercase 'county' (NOT 'COUNTY'), values UPPERCASE. production_status 10 distinct values (Producing/Producing PA Unit/Producing HBU/Primary term/Extended term/Drilling/Pooling/Shut in/Suspended/Unit communitization). record_status degenerate (all 851 = Active on active layer; all 5526 = Inactive on inactive layer).

Available Tools

  • searchOilGasLeases
    SITLA active O&G mineral leases (~851). Filter productionStatus/customer/leaseClass. NO county — bbox/near only.
  • searchInactiveLeases
    SITLA historical/expired O&G leases (~5.5K). Dates are MM/DD/YYYY strings (NOT epoch). NO county column.
  • searchSurfaceOwnership
    SITLA surface land ownership (~16K). Filter county/owner/agency. SITLA-only via sitlaOnly:true.
  • getLeaseDetail
    Single-lease lookup by leasegis (e.g. ML22161.0). Pass source:'inactive' for historical.
  • 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 School & Institutional Trust Lands with the energy switch.

Call the sitla MCP tool — start with method=searchOilGasLeases or method=searchSurfaceOwnership.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect UT School & Institutional 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

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 UT School & Institutional 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

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 UT School & Institutional 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

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:

"UT School & Institutional 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"
}