NSTA UK — Offshore & Onshore logo

NSTA UK — Offshore & Onshore

Live

UK North Sea Transition Authority — offshore and onshore wells, fields, licences, pipelines, discoveries, and round areas.

What is NSTA UK — Offshore & Onshore?

North Sea Transition Authority (NSTA) public petroleum data for the UK — UKCS offshore wells and fields, onshore wells (2,138 records across England, Scotland, and Wales), petroleum licences (PEDL, PL, ML, and more), SDC infrastructure pipelines, licence subareas, undeveloped discoveries, and 33rd-round indicative areas. Toggle on and use — no setup needed.

Available Tools

  • searchWells
    Search UKCS offshore wells by operator, licence, or location
  • searchOnshoreWells
    Search UK onshore wells by operator, county, or status
  • getOnshoreWell
    Full onshore well record by WELLREGNO
  • searchFields
    Search UK hydrocarbon fields (offshore or onshore) by name, operator, or status
  • getField
    Full field record by name (e.g. FORTIES)
  • searchLicences
    Search UK petroleum licences by type, reference, or operator
  • getLicence
    Full licence record by LICREF (e.g. PEDL137)
  • searchPipelines
    Search UKCS offshore pipelines by fluid, status, or operator group
  • searchSubareas
    Search UKCS offshore licence subareas by block, operator, or round
  • searchUndevelopedDiscoveries
    Search UKCS undeveloped discoveries by HC type or name
  • searchRoundIndicativeAreas
    List 33rd licencing round indicative areas
  • searchCarbonStorage
    Search current UKCS carbon storage licence areas

Requirements

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

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Open /mcp and turn on NSTA UK — Offshore & Onshore.

Call the nsta MCP tool with method=searchOnshoreWells or method=searchWells.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect NSTA UK — Offshore & Onshore 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 NSTA UK — Offshore & Onshore 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 NSTA UK — Offshore & Onshore 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:

"NSTA UK — Offshore & Onshore-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"
}