AK Oil and Gas Conservation Commission logo

AK Oil and Gas Conservation Commission

Live

Alaska Oil and Gas Conservation Commission well registry — North Slope (Arctic Slope, ~8.1K wells) plus Cook Inlet Basin (~1.75K). Hilcorp / ConocoPhillips / BP / ARCO operator side. No credentials required.

What is AK Oil and Gas Conservation Commission?

Alaska Oil and Gas Conservation Commission (AOGCC) statewide oil and gas well surface and bottom-hole locations. ~10,307 records per layer, all AK O&G wells regulated by the Commission. Top operators: Hilcorp Alaska 3,866; ConocoPhillips Alaska 2,745; BP Exploration Alaska 1,523. Top basins: Arctic Slope 8,135 (78.9%); Cook Inlet 1,750. Methods filter by area (basin), operator, status, well class, field, offshore-only, and bbox/near. Returns API number, permit number, current/permitted class+status, spud/completion/release dates, total/true vertical depth, surface and bottom-hole lat/lon. AK is borough-based — there is no county column; geographic scoping uses GeographicArea or bbox. ; responses normalized to WGS84. Last verified live 2026-05-07.

Available Tools

  • searchWells
    AOGCC wells (~10.3K). Filter area (basin name), operator, status (descriptive substring), wellClass (Development/Service/Exploratory/Stratigraphic Test), field, offshoreOnly. bottomHole=true switches to bottom-hole layer.
  • searchBottomHoles
    Bottom-hole locations (~10.3K) — same schema, deviated/horizontal end points.
  • getWellByApi
    Single well lookup by APINumber (14-digit, e.g. 50029201810000).
  • listLayers
    Catalog summary — services exposed and their URLs.
  • getServiceInfo
    Schema, record counts, enum values for surface and bottom-hole services.

Requirements

  • Toggle on
    Toggle on and use — no setup needed.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Open /mcp and enable AK Oil and Gas Conservation Commission with the toggle — no credentials needed.

Call searchWells with area: 'ARCTIC SLOPE' or 'COOK INLET BASIN' to explore well inventory.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect AK Oil and Gas Conservation Commission 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 AK Oil and Gas Conservation Commission 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 AK Oil and Gas Conservation Commission 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:

"AK Oil and Gas Conservation Commission-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"
}