Plugin documentation
TetraSoft Well Data
A free plugin that lets an AI assistant answer three common questions about U.S. oil and gas wells from state regulators' public records: what an API well number means, how to convert natural gas between volume and energy units, and how many wells are recorded near a location. It is for landowners, mineral and royalty owners, landmen, analysts and anyone reading well paperwork. It needs no account and no sign-in.
https://tetrasoftco.com/well-data/mcp Connect it
Claude
On a Free, Pro, Max or Ultra plan:
- In Claude, open Plugins in the sidebar.
- Select Add, then Add custom connector.
- Enter the name TetraSoft Well Data and the URL
https://tetrasoftco.com/well-data/mcp, and add it. The plugin needs no sign-in. - Start a new chat and ask one of the example prompts below.
On a Team or Enterprise plan, an Owner adds the connector for the organization in its organization settings, and members can then turn it on. The Free plan allows one custom connector. Claude's menus change from time to time; Anthropic's guide has the current steps: Add a connector by URL.
ChatGPT
The plugin is listed in ChatGPT as TetraSoft Well Data.
Other MCP clients
Any client that supports remote MCP servers over Streamable HTTP can connect to the URL above with no authentication.
The three tools
All three are read-only: they look things up and change nothing.
decode_api_number: Decode an API well number
Give a 10-, 12- or 14-digit API number, with or without dashes. It returns the state, county, unique well identifier, and any directional sidetrack and event sequence codes. It says where to look the well up: TetraSoft's state data page and TetraSoft Atlas for the eight covered states, or the state regulator's own well search for other states, plus TetraSoft's API county-code table for the state where one is published. Decoding explains the number's structure; it does not confirm that a well with that number exists.
convert_gas_volume: Convert gas volume and energy units
Converts between Mcf, MMBtu (dekatherms) and therms. Volume and energy only convert through the gas's heating value, so the tool uses the value you give, else the median of sampled gas analyses for the state you name (available for the eight covered states), else the U.S. average of 1,037 Btu per cubic foot from the U.S. Energy Information Administration. Every answer says which value it used and where it comes from.
find_wells_near: Count wells near a location
Give a U.S. street address, a 5-digit ZIP code or a latitude and longitude, and a radius of 0.5, 1, 2 or 5 miles (1 if you give none). It returns how many oil and gas wells state regulators have recorded within that radius, broken down by state and by each state's own well-status labels (for example producing, plugged, permitted). It returns counts only, never individual wells, with a link to each state's TetraSoft data page and to that state in TetraSoft Atlas.
Example prompts
- What does API number 42-501-20130-03-00 mean, and where can I look the well up?
- Which state and county is well 01-073-20001 in, and where do I look it up?
- How many oil and gas wells are within 2 miles of ZIP 43725?
- Are there gas wells within 5 miles of 39.6295, -79.9559?
- Convert 5,000 Mcf of Texas gas to MMBtu and therms.
Coverage and limits
- Well counts cover eight states: Colorado, New Mexico, Ohio, Oklahoma, Pennsylvania, Texas, West Virginia, Wyoming. Outside them a count of zero means the area is not covered, not that it has no wells, and the answer says so.
- API number decoding covers every state with an assigned API state code.
- Counts only. The plugin returns no well names, operators, exact locations, production or ownership data.
- Status is as current as each state's records. Where a state's status data is dated (Texas reports the month of its latest status update), the answer says so.
- Search limits.
find_wells_nearallows 5 searches a minute for each ChatGPT user. Claude users share 60 searches a minute between them, because Claude sends no per-user identifier. Other callers are allowed 5 a minute per network address. The other two tools have no limit. - Reference information only, not legal, title, environmental or investment advice.
Where the data comes from
Well records come from the official bulk data files and public data services each state's oil and gas regulator publishes. Every answer names the agency and dataset it draws on, with a link to the agency's page.
| State | Regulator |
|---|---|
| Colorado | Colorado Energy and Carbon Management Commission |
| New Mexico | New Mexico Oil Conservation Division |
| Ohio | Ohio Department of Natural Resources |
| Oklahoma | Oklahoma Corporation Commission |
| Pennsylvania | Pennsylvania Department of Environmental Protection |
| Texas | Railroad Commission of Texas |
| West Virginia | West Virginia Department of Environmental Protection |
| Wyoming | Wyoming Oil and Gas Conservation Commission |
Gas heating values come from gas analyses sampled by the Colorado regulator and the U.S. Geological Survey. The only live outside service the plugin calls is the U.S. Census Bureau's public Geocoder, for street addresses.
Troubleshooting
When a tool cannot answer, it says why and what to try. The common messages:
- "... is not an API number" or "... has N digits"
- Give the 10, 12 or 14 digits of the API number. Dashes, spaces and an "API" prefix are fine; letters and other characters are not.
- "State code NN is not assigned"
- The first two digits are the state code (01 to 51 onshore, for example 42 for Texas). Check the number for a typo.
- "No match for that address"
- Include the street number, city and state, or give a 5-digit ZIP code or a latitude and longitude instead.
- "The address service did not respond"
- Street addresses are looked up with the U.S. Census Bureau Geocoder, which was unavailable. Try again shortly, or use a ZIP code or coordinates, which need no outside service.
- "... is not a U.S. ZIP code area"
- Some ZIP codes (for example post-office boxes only) have no Census ZIP code area. Use a street address or coordinates.
- "... is not in the United States"
- Give latitude first, then longitude. Longitudes in the United States are negative.
- "A radius of N miles is not offered"
- Choose 0.5, 1, 2 or 5 miles.
- "The well search is limited to N searches a minute"
- Wait the number of seconds the message gives, then ask again. See Coverage and limits above.
- "Unit ... is not supported"
- Use Mcf, MMBtu (also written Dth or dekatherms) or therms.
- "A heating value of N Btu/scf is outside the plausible range"
- A natural gas heating value is between 300 and 2,500 Btu per standard cubic foot. Check the value on the gas analysis.
- "Well counts for ... are unavailable right now"
- A state's records are temporarily not loaded. Counts there are missing, not zero. Try again later.
- The connector will not connect
- Check the URL is https://tetrasoftco.com/well-data/mcp and that the connector was added with no sign-in. The plugin has no accounts, so there is nothing to sign in to.
Privacy and terms
The plugin has no accounts and stores no searched addresses, ZIP codes or coordinates. It keeps only anonymous daily counts. Read the Well Data Plugin Privacy Policy and the Well Data Plugin Terms of Use.
Support
Questions, problems, data corrections or security concerns: arthur.santos@tetrasoftco.com or jerry.duggan@tetrasoftco.com, or use the contact page. TetraSoft LLC, Fort Collins, Colorado.