NZP&M New Zealand Petroleum logo

NZP&M New Zealand Petroleum

Live

New Zealand petroleum permits, wells, and geophysical surveys — Taranaki Basin and beyond.

What is NZP&M New Zealand Petroleum?

NZ Petroleum & Minerals (MBIE) public ArcGIS data — 38 active petroleum permits, 1,267 wells, and 216 geophysical surveys (2007-2017). Covers exploration, mining permits, and mining licences primarily in the Taranaki Basin (NZ's only producing onshore/offshore basin). Well data includes type, content (oil/gas/dry), status, spud and completion dates, and depths. Production volumes are published separately by MBIE as PDF/Excel; this connector covers spatial and regulatory data. Toggle on and use — no setup needed.

Available Tools

  • searchPermits
    Search active NZ petroleum permits. Filter by type (Exploration/Mining Permit/Mining Licence), operator, status, basin, or bounding box.
  • getPermit
    Get a single permit by number (e.g. '38086'). Returns full attributes including operator, area, commencement, and expiry dates.
  • searchWells
    Search 1,267 NZ petroleum wells by type, operator, status (producing/shut in/P&A), content (oil/gas/dry), or bounding box.
  • getWell
    Get a single well by FullName (e.g. 'MA-10A', 'Kapuni-D09'). Returns depths, spud date, content, and status.
  • searchSurveys
    Search 216 NZ geophysical surveys (2007-2017) by type, company, region, or year.
  • getServiceInfo
    Record counts, all enum values, and notes on production-data limitations and block-offer data sources.

Requirements

  • No setup required
    Toggle on and use — no API key or credentials needed.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Open /mcp and enable NZP&M New Zealand Petroleum with the toggle.

Call searchPermits to find active permits or searchWells for petroleum wells.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect NZP&M New Zealand Petroleum 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 NZP&M New Zealand Petroleum 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 NZP&M New Zealand Petroleum 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:

"NZP&M New Zealand Petroleum-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"
}