Enverus

featured

Live

Enverus v3 direct-access connector with 109 dataset endpoints, access-aware discovery, and generic query/count/docs/ddl helpers.

What is Enverus?

Enverus in PatchOps supports both purpose-built helpers (wells, rigs, production) and generic dataset access for the full v3 direct-access model. Use listDatasets() for the canonical catalog and listDatasets({ probeAccess: true }) to classify per-dataset entitlement before querying.

Available Tools

getBasins
List valid basin values for ENVBasin filters.
getRegions
List valid ENVRegion values.
getStateProvinces
List valid state/province codes used by filters.
getWells
Query wells with basin/state/region/operator filters and pagination.
getWellHeaders
Query lightweight well header records for fast lookup workflows.
getRigs
Query rig datasets (active/activity/search views) with filters and pagination.
getProduction
Query production records with operator/play-aware filtering.
getWellsForRig
Resolve wells for a rig name in one helper call.
listDatasets
Return canonical dataset names; optional probeAccess classifies entitlement per dataset.
query
Generic dataset query for any v3 path your key can access (for example: wells, well-headers, active-rigs).
count
Dataset count helper using HEAD with GET fallback.
docs
Dataset documentation helper (GET /{dataset}/docs).
ddl
Dataset DDL helper (GET /{dataset}/ddl?ddl=mssql|pg).
getAccessToken
Explicit secret-key token exchange (POST /tokens).
getTokenInfo
Backward-compatible alias for token inspection workflows.
in_
Helper for Enverus in(...) filter syntax generation.

Requirements

Enverus secret key or bearer token
Use ENVERUS_SECRET_KEY (recommended) or ENVERUS_BEARER_TOKEN.
Endpoint entitlements
Dataset access is key-specific; use listDatasets({ probeAccess: true }) to validate access.
Compatible AI agent
Works with Claude, ChatGPT, and other MCP-compatible agents

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Add ENVERUS_SECRET_KEY in PatchOps. The connector auto-exchanges and caches bearer tokens.

Run listDatasets({ probeAccess: true }) to classify accessible vs forbidden datasets for your key.

Add the Enverus MCP server URL from PatchOps /mcp to your AI agent configuration.

Use dedicated helpers for common tasks, then query/count/docs/ddl for endpoint-level workflows.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect Enverus 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

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 Enverus 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

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 Enverus 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

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:

"Enverus-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"
}