Operator search
Search operators and retrieve match context.
Developers
EnergyNetWatch MCP Setup Guide
Use the EnergyNetWatch MCP server to connect compatible AI tools and agents to approved oil and gas data workflows.
Before you start
Access, keys, and scope
- MCP access requires approval and may be scoped by dataset, geography, endpoint, and usage volume.
- Store credentials in environment variables or client secret inputs, never in prompts or screenshots.
- AI output should preserve caveats and should not imply complete coverage where coverage is partial.
- AI output should distinguish source records from inference.
Available tools
Current MCP tool categories
Operator profile
Fetch approved operator profile fields by id.
Operator permits summary
Summarize permit context for a supported operator.
Operator production summary
Retrieve supported production context for an operator.
Permit search
Search permit records by approved filters.
Well search
Search well records.
Well profile
Fetch a supported well profile by API number.
Well production
Fetch supported well production history.
Data availability
Check whether EnergyNetWatch has evidence for an operator, company, state, county, or workflow.
Setup
Client configuration
Package
Use the authenticated MCP package download in /settings/api after API or MCP access is approved.
Environment
Set ENERGYNETWATCH_API_KEY in the local MCP client environment. Do not paste keys into prompts.
Base URL
ENERGYNETWATCH_API_BASE_URL defaults to https://api.energynetwatch.com.
Checks
Run npm run check, npm run doctor, npm run smoke, and a real-key smoke only after creating a customer API key.
Client config
The package emits client-specific configuration snippets through npm run print-config.
export ENERGYNETWATCH_API_KEY="REDACTED_TEMP_TEST_KEY"
export ENERGYNETWATCH_API_BASE_URL="https://api.energynetwatch.com"
npm run check
npm run doctor
npm run smoke
npm run print-config -- --client codexClient guides
MCP setup by client
Codex
Use EnergyNetWatch MCP in a clean Codex workspace.
Open guideClaude Desktop
Configure a local MCP server block for Claude Desktop.
Open guideCursor
Connect Cursor to the local MCP server without storing keys in project files.
Open guideGeneric MCP client
Use the environment-based setup shape for compatible clients.
Open guideExample questions
Prompts for real-key smoke testing
Find operators with recent Texas drilling permit activity.
Check whether this operator has permit, well, production, or facility records.
Summarize recent activity for this county.
Build a lead list from recent infrastructure signals.
Compare activity between two operators.
Authentication
How credentials are handled
The local MCP server calls the EnergyNetWatch public API with `X-API-Key`. It should read the key from environment configuration supplied by the MCP client. The MCP server does not connect to RDS and should not print the key during checks or smoke tests.
Supported setup path
The current customer path is the authenticated local package download from `/settings/api`, then client configuration generated by the package. Hosted remote MCP and OAuth remain separate future work.
Safety
Safety and source context
- Include loaded-through dates and request ids where available.
- Verify high-stakes commercial decisions before acting on generated summaries.