What is Sodir (Norwegian Offshore Directorate)?
Norwegian Offshore Directorate (Sodir) factmap data for the Norwegian Continental Shelf. No credentials required — toggle on and use. Covers: wellbores (9,765 — filter by operator, status PRODUCING/P&A/PLUGGED, purpose WILDCAT/APPRAISAL/PRODUCTION, content OIL/GAS/DRY, field, production licence, North/Norwegian/Barents Sea area); fields (142 — Producing/Approved for production/Shut down); hydrocarbon discoveries (645 — with current activity status, HC type, linked field); production licences (1,809 active and historical polygons); offshore pipelines (82); facilities — platforms, FPSOs, subsea templates (1,215); seismic survey areas (5,008 — 2D/3D/4D); company registry (NCS operators and licensees). Per-wellbore sub-tables: formation tops (lithostratigraphy), drill stem tests (DST), narrative history (HTML), and field-level reserve estimates (oil/gas/NGL/condensate, multi-vintage back to first estimate). Probe date: 2026-05-04. Upstream quirks: field activity status field name contains a typo ('fldCurrentActivitySatus' — missing 't'); discovery geometry is Polygon not Point; seismic field prefix is 'sea' not 'seis'. Monthly production volumes are CSV-only at Sodir and are not in this connector — future ETL candidate. License: Norwegian Licence for Open Government Data (NLOD). Attribution: 'Source: Norwegian Offshore Directorate (Sodir)'.
Available Tools
Requirements
- Toggle OnToggle on and use — no credentials required. Enable the sodir energy connector at /mcp.
Quick Setup Guide
Follow these steps to connect your AI agents to this connector
Open /mcp and turn on Sodir (Norwegian Offshore Directorate) with the energy switch.
Call the sodir MCP tool — start with searchWellbores or searchFields. No API key needed.
Connect to Your AI Assistant
Choose your AI assistant below for specific setup instructions
Follow these steps to connect Sodir (Norwegian Offshore Directorate) 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 Sodir (Norwegian Offshore Directorate) 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 Sodir (Norwegian Offshore Directorate) 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:
"Sodir (Norwegian Offshore Directorate)-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"
}