Petrora exposes its data as a remote MCP server. MCP, the Model Context Protocol, is the open standard assistants use to call outside tools. Once Petrora is connected, you ask Claude questions in plain language, Claude calls Petrora's tools, and every answer links to the page that backs it.
Status: beta, free trial. The connector is live for every account; your free trial starts the moment you approve it, with nothing to request and no credit card (how it works). Signing in happens inside Claude when you add the connector. Menu names in Claude change occasionally, so look for "Connectors" if a label differs.
Claude on the web or desktop
- Open Settings, then Connectors.
- Choose Add custom connector.
- Name it
Petroraand enter the server URL:https://mcp.petrora.com/mcp - Click Add. Claude opens a Petrora page in your browser: sign in if you are not already, review what Claude will be able to read, and choose Allow. You are sent back to Claude with the connector ready.
- In a new chat, open the tools menu and make sure Petrora is enabled.
Custom connectors are available on paid Claude plans; on Team and Enterprise plans an admin may need to enable them first.
Claude Code
From a terminal:
claude mcp add --transport http petrora https://mcp.petrora.com/mcp
Then run /mcp inside Claude Code to authenticate; it opens the same Petrora page in your browser. The tools appear alongside your other MCP servers.
What to ask
Petrora's tools cover operators, wells, permits, production, disposal, and seismicity. Questions that work well:
- "Who filed the most Loving County permits this month, and what are they targeting?"
- "Show the chain of custody for API 42-337-34003."
- "Which disposal wells within 15 miles of Pecos had earthquakes near them this year?"
- "List Diamondback's permits in Martin County since July, newest first."
Claude will say which tool it called and link to the pages it used. If an answer has a number with no link, ask for the source; the tools always return one.
Tools your AI gets
Twenty-eight read-only tools, one per read on the public API, grouped by what they look at. Every result carries the petrora.com URL of each entity it names.
| Area | Tools |
|---|---|
| Coverage | data_coverage: what is on file per source and when it was last loaded. |
| Permits | search_permits (every filter the permits page has, with a total for paging), get_permit. |
| Counties | list_counties (ranked by 90-day activity, filter by district), get_county (the hub: windows, trend, top operators, new entrants, formations), county_operators. |
| Operators | search_operators (name search, active ranking, or the whole directory), get_operator (the hub), operator_permits, operator_wells, operator_in_county. |
| Wells | search_wells, get_well (permits, completions, chain of custody, production, tops, injection, seismicity, offsets), cross_section (tops for up to eight wells side by side). |
| Leases and fields | search_leases, get_lease (monthly production, operator runs, decline fit), lease_wells, search_fields, get_field. |
| Formations and basins | list_formations, get_formation, list_basins, get_basin. |
| Water and earthquakes | disposal_statewide, county_disposal, earthquakes_statewide, county_earthquakes, get_earthquake. |
Counties, formations, and basins take names or slugs ("Reeves County" works). Operators are keyed by RRC operator number; Claude calls search_operators first when it only has a name.
The API behind the tools
Each tool is a thin wrapper over the public REST API, so anything the connector can fetch you can also fetch directly. The interactive reference lists every endpoint, parameter, and field with a try-it client, and the OpenAPI document at /v1/openapi.json is the machine-readable version. Claude Code can read that document to write a script against the API without the connector, and a Claude Project can hold it as context so Claude knows the exact shapes it is working with. The written API reference explains the identifiers, windows, and lags.
Limits and privacy
The connector reads public record only, and Petrora stores which tools were called for metering and abuse prevention, never the conversation. Each tool call is one metered call against your trial or plan; a compound question is usually three to ten. Assistants you have signed in are listed on your account page, where you can disconnect any of them.