1
Connect an MCP-compatible client
Use an MCP client or internal AI workflow with EnergyNetWatch credentials stored securely.
Oil and gas MCP server
Oil and Gas MCP Server for AI Agents, Codex, Claude Desktop, and Cursor
Research operators, permits, wells, and supported production records from your AI client. Keep source dates and coverage notes alongside the answers.
Start with $50 for 2,500 prepaid API units. MCP uses the same API credits; no separate MCP plan or Premium app subscription is required. AI-provider charges are separate.
Already have credits? Open API Access to create a key and download the local MCP package once payment is processed and API access is active. This is a local package, not a hosted remote connector.
Current local release
Version 0.1.10 · 39 read-only tools · updated September 3, 2026
This release preserves all 36 tools from version 0.1.9 and adds three bounded Texas UIC injection/disposal tools.
- Connect Codex, Claude Desktop, Cursor, and compatible MCP clients
- Query operators, permits, wells, production context, TX/NM signal summaries, and infrastructure signals
- Use source dates and coverage notes in AI workflows
- Built for local MCP and agent workflows
- Supports research, lead generation, monitoring, and reporting
- Access can be configured by dataset, geography, and usage need
An example you can inspect before buying
Oil and gas MCP workflow: prepare an operator account brief
Before contacting an operator, identify where its permit activity appears and bring specific well records to the conversation. This Mewbourne example shows the evidence a sales or research team can work from.
Where does Mewbourne have permit activity?
The September 18, 2026 review returned 37 permit-date records: 25 in Eddy and 12 in Lea, with a June 20 lower date bound. Every returned operator label was MEWBOURNE OIL CO.
A separate REST reported-spud screen returned 42 records: 27 in Eddy and 15 in Lea. These are independent populations. Do not add them or treat them as a permit-to-drilling conversion rate.
This is an editorial brief based on retained API responses, not a recording of an AI session or a live count. A rolling-window query run today can return different records.
Three records from the 37-row permit sample
Filed operator: MEWBOURNE OIL CO. State: New Mexico. Missing spud dates do not prove drilling has not started.
RUNWAY 26 30 FEDERAL COM #557H
- API identifier
- 3001558956
- County / permit issued
- Eddy / 2026-09-11
- Reported spud date
- Not reported in reviewed row
PILE DRIVER 24 13 FEDERAL COM #528H
- API identifier
- 3002556872
- County / permit issued
- Lea / 2026-09-09
- Reported spud date
- Not reported in reviewed row
AWESOME BLOSSOM 24 23 FEDERAL COM #554H
- API identifier
- 3001558924
- County / permit issued
- Eddy / 2026-09-08
- Reported spud date
- Not reported in reviewed row
Enter your name, company and email to receive a verification link. No account or payment required. CSV dates use YYYY-MM-DD. Import API identifiers as text. The download contains selected fields from the permit-date population only, with retrieval time and source link.
Run operator research in your MCP client
After configuring the local package and key, use this prompt. Your AI client creates the brief from tool results; review its interpretation before using it.
Use energynetwatch_search_permits with state="NM", search="MEWBOURNE", days=90, limit=50, page=1. Inspect pagination and retrieve every remaining page before reporting totals. Check returned operator labels; text search is not a corporate-family match.
Prepare an operator account brief with county counts and a table of well name, API identifier (as text), issue date and reported spud date. Preserve missing dates. State when the records were retrieved and which date the search uses. Separate facts from interpretation and suggest three questions to investigate before sales outreach. Do not infer active rigs, purchase intent or an unreported drilling status.
For a separate spud-date population, ask me for a complete REST export using spuddedOnly=true. Do not silently substitute this permit-date search. Never ask me to paste an API key.The current MCP permit-search tool accepts state, lookback, search and pagination, with at most 50 rows per request. It has no native county or spuddedOnly filter. Use a complete REST export for those populations.
See the REST requests and operator data exampleWhat does this workflow cost?
Each permit-search request uses 6 API units. The retained 37-row permit response fits one 50-row MCP request: 6 units, equivalent to $0.12 of a $50 / 2,500-unit pack. The two historical REST screens used 12 units ($0.24 equivalent). This is data-request consumption, not a purchase price or a fixed cost for an AI conversation. Additional pages, retries and other tool calls cost more; AI-provider charges are separate.
The minimum credit purchase is $50. No Premium app subscription or separate standard MCP plan is required. After payment is processed and API access is active, create your key and download the local MCP package from API Access.
AI tool access
Give AI tools access to structured oil and gas data
AI tools are useful, but they need reliable structured data to answer operational questions. The EnergyNetWatch MCP server helps connect compatible AI tools and agents to oil and gas datasets exposed through EnergyNetWatch instead of asking a model to guess from generic web results.
API or MCP?
Use MCP when an AI client needs tools, not raw endpoints
Use direct API access for dashboards, CRMs, data pipelines, and backend services. Use MCP when an AI assistant or agent needs to call EnergyNetWatch tools inside a natural-language workflow while keeping API keys in the local client environment.
Follow the county REST export and MCP review workflowAsk an AI agent for operator activity.
Search permit records using state, date window and text search. For a complete county population, use a county-filtered REST API export first; the current MCP permit tool has no native county filter.
Query wells and supported production records.
Compare activity around a company or region.
Generate source-linked research outputs with caveats.
Check data availability before deeper analysis.
Practical setup
How EnergyNetWatch MCP works
2
The AI calls EnergyNetWatch tools
The AI can query tools for operators, permits, wells, production context, infrastructure signals, TX/NM signal summaries, and data availability.
3
Results return with source-aware oil and gas context
Responses should preserve coverage, freshness, loaded-through dates, caveats, and request context where available.
Prompt examples
Example MCP workflows
Find Texas operators with recent drilling permit activity.
Show me Civitas-related permit, well, production, and infrastructure context.
Review an attached complete county REST API export to build a dated Permian permit watchlist.
Which operators have new infrastructure or facility permit signals?
Summarize the current TX/NM signal report from PS-48, NM APD, facility, and midstream context.
Pull two Texas PS-48 construction-start notices and explain the caveats before using them in a lead list.
Create a lead list from recent permit activity and explain why each operator matters.
Check whether EnergyNetWatch has production, permit, and well coverage for this operator.
Summarize recent operator activity in a way a business development team can act on.
Compare two operators by recent permits, production context, counties, and infrastructure signals.
Find Texas UIC wells for an operator and summarize one well's H-10/H-10H history with the capacity caveat.
Tool surface
What can the 39-tool MCP server query?
Operators
Search and profile operators, review permit and production summaries, and compare top production operators.
Permits
Search permits, rank active operators, and compare permit-growth windows with all-time and trailing-period labels.
Wells
Search wells, retrieve well profiles, and query well-card snapshots or supported modeled monthly history.
Texas regulatory data
Query RRC identities, official lease production, completions, IWAR inactive status, OLTDW/Oil Masters context, and bounded UIC injection/disposal history with distinct dataset and row clocks.
Production
Keep official filed lease totals separate from existing modeled well history, with distinct source clocks and caveats.
Physical midstream
Query bounded Texas pipeline GIS, T-4 route evidence, and regulator-derived Texas or New Mexico facilities.
Infrastructure signals
Search facility permits and operator leads where EnergyNetWatch has supported source coverage.
TX/NM signals and midstream
Query TX PS-48, NM APD, combined signal summaries, and verified midstream project announcements.
Availability and API health
Check coverage before deeper analysis and confirm the API service is available.
MCP vs API access
Use the API when a software system needs direct endpoint access to EnergyNetWatch records. Use the MCP server when an AI assistant, agent, or MCP-compatible client needs to call EnergyNetWatch tools inside a natural-language workflow.
Source-aware AI workflows
Oil and gas records can be incomplete, state-specific, delayed, or loaded through different dates. MCP workflows should preserve source context, loaded-through dates, coverage status, and caveats wherever possible.
Fit
Who should use the EnergyNetWatch MCP server?
Developers
Connect EnergyNetWatch tools to MCP-compatible clients, AI applications, and internal agent workflows.
Business development teams
Ask natural-language questions about operators, permits, counties, infrastructure signals, and lead lists.
Analysts
Use AI to summarize records, identify changes, and prepare recurring briefs from structured data.
AI builders
Give agents oil and gas tools instead of relying on unstructured search or manual data uploads.
Small teams
Start with focused access before investing in a larger custom data workflow.
Access
Access and pricing
Start with $50 for 2,500 prepaid API units. Once payment is processed and API access is active, create a key and download the MCP package from Settings → API Access. You do not need a separate MCP plan or a Premium app subscription. Your AI client must support the documented connection; AI-provider charges are separate from EnergyNetWatch units.
FAQ
Oil and gas MCP server questions
What is an MCP server?
An MCP server lets compatible AI tools connect to external systems, data sources, and tools. For EnergyNetWatch, the MCP server lets AI workflows query structured oil and gas data through controlled tools.
How is MCP different from an API?
An API is used directly by software systems through endpoint requests. MCP is designed for AI tools and agents that need to call tools in a natural-language workflow. The API is best for direct integrations, while MCP is best for AI-assisted research, monitoring, and workflow automation.
What oil and gas data can the MCP server access?
Available tools use your API key scopes and account limits to access operators, permits, wells, supported production context, facility permits, infrastructure signals, TX PS-48 notices, NM APD records, TX/NM signal summaries, and data availability checks. Coverage varies by dataset and state.
Do I need a separate MCP plan or Premium subscription?
No. Standard MCP setup is available with active API-only prepaid access. Buy API credits, create a key, and download the MCP package from API Access. Calls use the same API unit balance; your AI provider may charge separately. Custom delivery or support can be scoped separately.
Can I use this with ChatGPT, Claude, or other AI tools?
EnergyNetWatch MCP access is intended for compatible AI tools and MCP-style workflows. Availability depends on the client, configuration, authentication, and endpoint access.
Is MCP access included with API access?
Yes. Standard MCP setup is available with active API access and uses the same key scopes and API unit balance. No separate standard MCP plan is required. Your AI provider may charge separately.
Can an AI agent use this to generate oil and gas lead lists?
Yes, where the tools and available data support the workflow. Example use cases include operator research, permit monitoring, county watchlists, PS-48/APD signal review, infrastructure signals, and business development lead scoring.
Does the MCP server preserve source context?
It should. MCP workflows should expose source and coverage context where possible, including loaded-through dates, caveats, and request IDs.