Texas RRC Data logo

Texas RRC Data

Live

Texas Railroad Commission wells, lease production, and pipeline data from PostGIS.

What is Texas RRC Data?

Texas Railroad Commission data including statewide well locations, lease-level monthly production (oil, gas, condensate), and pipeline segment geometries. Search wells by operator, county, type, status, bounding box or proximity. Retrieve production history by API number, query lease production maps, and render pipeline GeoJSON for siting workflows.

Available Tools

  • searchWells
    Search RRC wells by operator, county name or code, type, status, bbox, or proximity (flat lat/lon/radius).
  • searchWellsByArea
    Search wells within a geographic area (flat lat/lon/radius or bbox).
  • getWellDetail
    Get a single well by API number.
  • getWellProduction
    Get production history for a well by API number.
  • searchProductionByArea
    Search lease production data by area with optional filters.
  • getProductionGeoJSON
    Get lease production as GeoJSON FeatureCollection for map rendering.
  • searchPipelineSegments
    Search pipeline segments by number, bbox, or nearby point.
  • getPipelineGeoJSON
    Get pipeline data as GeoJSON for map rendering.
  • listPipelines
    List available pipeline numbers with pagination (limit/offset).
  • getDataStatus
    Summarize loaded well, production, and pipeline datasets.
  • getPipelinesNearLocation
    Find pipelines near a coordinate.

Requirements

  • No authentication required
    Free public RRC data — no API key needed

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

This is a free public data connector with no authentication.

Search Texas wells, get production data, or render pipeline maps.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect Texas RRC Data 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 Texas RRC Data 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 Texas RRC Data 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:

"Texas RRC Data-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"
}