EMODnet Human Activities logo

EMODnet Human Activities

Live

Pan-EU harmonized offshore oil & gas — wells, pipelines, platforms, and licences across 18 European countries.

What is EMODnet Human Activities?

EMODnet Human Activities delivers harmonized offshore energy data across 18 EU countries: Croatia, Cyprus, Denmark, Faroe Islands, France, Germany, Greece, Ireland, Italy, Latvia, Malta, Montenegro, Netherlands, Norway, Poland, Portugal, Spain, and the United Kingdom. Four feature types: offshore wells (~28,500 points with status/purpose/content/operator), platforms (~1,600 with structure type and production commodity), pipelines (~3,950 lines with medium and operator), and active petroleum licences (~1,300 polygons). Annual update cadence — use as a pan-EU breadth layer. For authoritative national data prefer dedicated connectors (NSTA for UK, Sodir for Norway). Protocol: OGC WFS 2.0.0 with CQL filters — the first WFS connector in PatchOps.

Available Tools

  • searchWells
    Offshore wells (hydrocarbons layer, ~28,500 features). Filter by country, status, purpose, content, operator, or bbox.
  • searchPlatforms
    Offshore platforms (~1,600 features). Filter by country, currentStatus, category, primaryProduction, or operator.
  • searchPipelines
    Offshore pipelines (~3,950 line features). Filter by country, status, medium (Gas/Oil/Condensate), or operator.
  • searchLicences
    Active petroleum licences (~1,300 polygon features). Filter by country, type, or operator.
  • getServiceInfo
    Feature counts per layer, enum value lists, 18-country coverage, and Section-0 probe notes.

Requirements

  • Toggle on
    Toggle on — no setup needed.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Open /mcp and turn on EMODnet Human Activities 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 EMODnet Human Activities 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 EMODnet Human Activities 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 EMODnet Human Activities 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:

"EMODnet Human Activities-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"
}