Getting Started with the Drill2Frac MCP

What is the Drill2Frac MCP?

The Drill2Frac MCP is a unified data platform for completion engineering. It brings together the data you need to design, validate, and compare hydraulic fracturing programs — well metadata, drilling curves, stage and cluster schedules, and FlowFX simulation results — and exposes it as a queryable building block for AI agents.

You don't need to know Globally Unique Identifiers (GUIDs), write queries, or click through dashboards. You ask in plain language; Claude (or any MCP-aware agent) pulls the right records and presents them.

The same dataset feeds two audiences:

• Our internal agentic workflows — the pre-completion agent (currently available: gamma-ray-driven stage scheduling and cluster placement; coming soon: RockMSE, post-completion analysis, and more) and whatever we build next consume Drill2Frac MCP the same way you do.
• Our customers' AI agents — same MCP, same data, alongside whatever other MCPs they've connected (financial, scheduling, reservoir, ops). Drill2Frac data becomes a composable input to their agentic stack.

**The connection is read-only. Every tool the server exposes is a query. Nothing your AI assistant does through the MCP connection can change, delete, or publish anything in Drill2Frac.

Setup

Drill2Frac data is exposed through an MCP (Model Context Protocol) server — the open standard Anthropic, OpenAI, Google, Microsoft and others have agreed on, so the same connector works with any modern AI agent. You add the server address once, sign in with your Drill2Frac credentials, and from then on the tools are available in any new chat.

You need exactly one piece of information:

https://mcp.drill2frac.ai/mcp

Setup at a glance

There is nothing to install, and no administrator rights are required. Choose the instructions for the AI assistant you use.

⚠️ You are dealing with two completely separate accounts. This trips almost everyone up.

• Your Claude or ChatGPT account — email, password, subscription. Nothing to do with Drill2Frac.
• Your Drill2Frac credentials — a different username and password on our website, plus multi-factor authentication.

A problem with one is not a symptom of the other. If the AI assistant won't let you sign in, that's Anthropic or OpenAI. If the well data won't load, that's Drill2Frac.

Step 1 — Which account you need

OpenAI has two separate products here, and they have different rules. This is the single biggest source of confusion, so check which one you are using before anything else.

If you are on ChatGPT Plus, you are not locked out — you just cannot use the web app's custom connectors. On a Plus account, developer mode switches on but the option to create a connector never appears, and OpenAI's own documentation is wrong on this point. Use Codex instead, which works on Plus and reaches the same data. Confirmed on a Plus account.

Either of ChatGPT's two Pro tiers works; the difference between them is usage limits, not features. Free and Go cannot add connectors at all.

Claude is the smoothest of the three, and it works on every plan including Free. If you have a choice, start there.

Step 2 — Get Microsoft Authenticator ready

You do not need to visit a website first. Everything happens during the connector sign-in in Step 3: you enter your email and password, and if you have never set up two-step verification, the same page walks you through it there and then.

The one thing worth doing in advance is installing the app, because you will need it on your phone partway through Step 3.

1. Install Microsoft Authenticator on your phone. There are several similarly-named authenticator apps in the app store — make sure you get the Microsoft one.
2. That is all. Continue to Step 3.

Setting up two-step verification

This happens on the Drill2Frac sign-in page that opens during Step 3, once you have entered your email and password. If you have set it up before, you will simply be asked for a code and can skip this section.

1. The page shows a QR code, and beneath it the same key written out as text in case your camera will not cooperate.
2. In Authenticator, tap + to add an account and choose Other — not "Work or school account".
3. Scan the QR code, or choose to enter a key manually and type in the one shown. A new entry appears in your list labelled Drill2Frac Services, showing a rotating 6-digit code.
4. Back in the browser, type the current 6-digit code into the box — no space in the middle, even though the app displays one — and submit it.

That code both proves the setup worked and completes your sign-in. Nothing is saved against your account until it does, so if you abandon this partway through, you start cleanly next time rather than being half-enrolled.

If you also use the Drill2Frac website, this is the same two-step verification. Setting it up in either place covers both — you do not do it twice.

If the code is rejected:

• The codes rotate roughly every 15–30 seconds. If you took too long reading it off your phone, the code expired before you hit submit. A red error here usually means nothing more than that. Grab the current code and submit again. It commonly takes two or three tries.
• If it keeps failing, close the sign-in window and start Step 3 again. A fresh sign-in page gets you a fresh code box, which clears up most repeat failures.
• New phone? Authenticator entries don't always migrate across devices, even with an Apple ID restore. If that entry didn't come across, just re-enroll from scratch.

⚠️ Security note. During setup you may receive unrelated SMS messages saying things like "here is your link verification code." If you didn't request it, it is not part of this process. Don't click anything in it and don't type the code anywhere. Nothing in Drill2Frac MFA enrollment arrives by text message — the codes come from the Authenticator app on your phone and nowhere else.

Step 3 — Add the connector

Step 3a — Connecting in Claude

On Free, Pro, or Max, you add it yourself. Do this on claude.ai in a browser even if you mainly use the desktop app — see Using the Drill2Frac MCP in Claude Desktop for why:

1. Open claude.ai and go to Settings → Connectors.
2. Choose Add custom connector.
3. Paste the server address: https://mcp.drill2frac.ai/mcp
4. Leave the OAuth client setting on "No client ID — register one automatically". This is the default, and it is the correct choice — our server supports automatic registration. Do not pick "Use Anthropic's hosted client metadata"; our server does not support that method and it will fail.
5. Click Connect. A Drill2Frac sign-in page opens.
6. Sign in with your Drill2Frac email and password — not your Claude credentials.

That is the whole setup.

On Team or Enterprise, an Owner has to add it for the organization first:

1. An Owner goes to Organization Settings → Connectors → Add → Custom and enters the server address above. This makes the connector available; on its own it grants nobody access to any data.
2. Each person then goes to Settings → Connectors and clicks Connect next to Drill2Frac MCP, signing in with their own Drill2Frac credentials.

If you are on Team or Enterprise and cannot find Add custom connector, that is expected and is not a fault. Ask an Owner to complete step 1.

Using the Drill2Frac MCP in Claude Desktop

Add the connector on claude.ai in a browser, not in the desktop app. Connectors belong to your Claude account, so one added on the web appears in Claude Desktop by itself — there is nothing separate to install or configure.

Doing it the other way round causes a problem that is not obvious. If you add it in Claude Desktop first, the web will not let you add the same URL again — it is already registered to your account, and you are left with a connector the desktop app has but the web does not offer to manage. The way out is to remove it in Desktop, add it on the web, and let Desktop pick it up again. Starting on the web avoids the round trip entirely.

Where to find it. The menus move between releases. Connectors have appeared under Settings → Connectors and under Customize; if one is not there, look for the other.

If it still does not appear in Desktop, fully quit and reopen it. In our experience the desktop app reads the account's connector list at launch rather than picking up a new one immediately. Anthropic does not document this either way, so treat it as a reliable fix rather than a required step. "Fully quit" means exactly that, and the X button is not enough:

• Windows: File → Exit, or right-click the system-tray icon and choose Quit.
• macOS: Cmd+Q, or right-click the Dock icon and choose Quit. Closing the window leaves Claude running.

On ChatGPT Plus? Neither of the two sections below applies to you. Go to OpenAI Codex instead.

Step 3b — Connecting in ChatGPT on the web

This is the chatgpt.com web app, which is a different thing from Codex. It requires Pro or above, and the option sits behind a developer setting. On Plus, skip this and use Codex.

1. Confirm your plan. Free, Go, and Plus cannot do this — Plus users should use Codex.
2. Open Settings → Plugins and switch on Developer mode. On Business and Enterprise a workspace admin can disable this or restrict it to an approved list, so check with your IT team if the toggle is missing.
3. Close Settings, then click Plugins in the sidebar.
4. Click the + button, next to the search box at the top right of that panel.
5. In New Plugin, fill in: - Name — Drill2Frac MCP - Description — optional, leave blank if you like - Connection — leave the toggle on Server URL (not Tunnel) and enter https://mcp.drill2frac.ai/mcp - Authentication — OAuth. You do not need to open Advanced OAuth settings; the server publishes what ChatGPT needs.
6. Tick I understand and want to continue under the risk warning, then click Create.
7. Sign in with your Drill2Frac credentials when the browser window opens.

The wording moves between releases. OpenAI has called this feature Connectors, Apps and now Plugins, and the menus have moved with it. If Plugins is not where this says, look for Apps or Connectors — the sequence is the same: turn on developer mode in Settings, then add the server from the sidebar.

Worth knowing about the ChatGPT web app:

• Custom connectors are still labeled as in development. Expect the menus and behavior to change.
• Tools are not available in shared chats. A connector belongs to your account, so if you share a conversation the recipient cannot re-run anything it did.
• ChatGPT applies its own rate limits on top of ours, so very large or repeated requests may be throttled.

Step 3c — Connecting in OpenAI Codex

Codex is not the ChatGPT web app. It is OpenAI's coding AI assistant, and it comes in three forms that all share one configuration file:

• the Codex desktop app
• the VS Code / IDE extension (shipped inside the ChatGPT extension)
• the command-line tool

Set it up once and all three work. Crucially, Codex works on ChatGPT Plus, where the web app's custom connectors do not — so this is the route for anyone on Plus.

Easiest — let Codex configure itself

Codex can edit its own configuration, so you do not have to find the file. Open a Codex chat and paste this in:

Please add or verify the Drill2Frac MCP server in my Codex config:
https://mcp.drill2frac.ai/mcp
Use the server name Drill2Frac MCP.

Expected steps:

1. Open my Codex config at ~/.codex/config.toml (on Windows,
   C:\Users\<your-username>\.codex\config.toml).

2. Check whether [mcp_servers.Drill2Frac MCP] already exists.

3. If it does not exist, add it with:
   url = "https://mcp.drill2frac.ai/mcp"

4. If a test Drill2Frac MCP server exists, compare the per-tool approval
   settings and keep
   the original server consistent where appropriate.

5. Validate that the TOML configuration file (a file that stores application settings) file still parses correctly.

6. Confirm Codex can see the server. On Windows the codex executable is
   usually NOT on PATH -- it ships inside the ChatGPT desktop app and the
   VS Code extension, under a folder that changes with every update. Do
   not assume a bare "codex" command works. Resolve it first:

     $codex = Get-ChildItem -ErrorAction SilentlyContinue -Path @(
         "$env:LOCALAPPDATA\OpenAI\Codex\bin\*\codex.exe",
         "$env:USERPROFILE\.vscode\extensions\openai.chatgpt-*\bin\windows-x86_64\codex.exe"
       ) | Sort-Object LastWriteTime -Descending | Select-Object -First 1

   then run:
     & $codex.FullName mcp get Drill2Frac MCP
     & $codex.FullName mcp list

7. Check basic network reachability for mcp.drill2frac.ai
   over HTTPS.

8. Tell me whether the server is configured, enabled, reachable, and
   whether a restart or a sign-in is needed before live tool testing.

   If a sign-in is needed, give me the exact PowerShell to paste, using
   the resolved path from step 6:

     & $codex.FullName mcp login Drill2Frac MCP

   Do NOT give me a bare "codex mcp login" command. It fails with
   "not recognized" on a normal Windows install and looks like the server
   is broken when it is not.

9. Do not claim the MCP tools were fully smoke-tested unless the tool
   namespace is actually
   available in the current Codex task and live tool calls were made.

Codex will report back on each point. Step 9 is important because it requires Codex to actually test an MCP tool rather than simply report that the connection appears to be working. happily tell you the tools are working when it has never called one.

When it is done, you still need to sign in — see Signing in below. Editing the config tells Codex where the server is; it does not authenticate you.

If you would rather edit the file yourself

The config file is:

C:\Users\<your-username>\.codex\config.toml

On macOS and Linux, ~/.codex/config.toml. The folder is hidden on Windows — paste the path straight into Explorer's address bar, or open it from a terminal. If the file does not exist, create it.

Add this at the end. It is TOML, so section order does not matter, but do not paste it inside another [section]:

[mcp_servers.Drill2Frac MCP]
url = "https://mcp.drill2frac.ai/mcp"

That is Codex's native HTTP support — it talks to our server directly over HTTPS. There is nothing to install.

Signing in

However you added the server, the login is a separate step.

Codex is included with the ChatGPT desktop app and the VS Code extension, and neither puts codex on your PATH. Typing codex in a terminal fails even though Codex is installed and working. Both locations also carry a version or hash in the path, so they change every time Codex updates — a path you write down today stops working next month.

Paste this into PowerShell. It finds the newest copy wherever it lives, then runs the login:

$codex = Get-ChildItem -ErrorAction SilentlyContinue -Path @(
    "$env:LOCALAPPDATA\OpenAI\Codex\bin\*\codex.exe",
    "$env:USERPROFILE\.vscode\extensions\openai.chatgpt-*\bin\windows-x86_64\codex.exe"
  ) | Sort-Object LastWriteTime -Descending | Select-Object -First 1

& $codex.FullName mcp login Drill2Frac MCP

A browser window opens for the Drill2Frac sign-in. Use your Drill2Frac credentials.

To run any other Codex command the same way, keep $codex from above and call & $codex.FullName <command>.

If you would rather have codex on your PATH, add the folder the snippet resolved to — print it with $codex.DirectoryName — to your user PATH environment variable. It will need updating when Codex next updates itself.

Checking it worked

& $codex.FullName mcp list

Look at the last two columns for Drill2Frac MCP:

In the Codex TUI you can also run /mcp. Then verify with "What wells are available in Drill2Frac?"

Step 4 — Verify it worked

Start a new chat and ask:

"What wells are available in Drill2Frac?"

You should get a list of the wells your Drill2Frac account can already see. If the count looks right, you are done.

Staying signed in

Once you have connected, the connection renews itself in the background. You do not need to sign in every day, and you do not need to do anything after a normal weekend or a long holiday weekend.

There are two clocks behind it:

The second clock is the one worth knowing. It measures inactivity, not age. A connection you use every week keeps working indefinitely — it never expires just because it is old. One of our longest-running connections renewed itself twenty times across eighteen days without anyone signing in again.

Coming back from time away

A two-week vacation lands almost exactly on the 14-day limit, so treat it as a coin toss. If you would rather not find out on your first morning back, open a chat and ask the connector anything at all before you leave for the second week — that resets the clock.

Reconnecting takes under a minute. If your connection expires, your AI assistant will no longer be able to access Drill2Frac data, and you'll be prompted to authorize the connection again. Open your connector settings, click Connect, and sign in as you did originally. Nothing is lost. Your chats, history, and permissions remain unchanged. chats, your history, and your permissions are all unchanged.

Changing your password

Changing your Drill2Frac password signs you out everywhere except where you change it.

Every AI assistant you have connected — Claude, ChatGPT, Codex — stops returning answers and asks to be connected again. So does the Drill2Frac website in any other browser, on any other machine. The same happens if an administrator resets your password for you.

The browser where you change your password remains signed in. You can continue working without being redirected to the login page part-way through what you were doing, and you are not asked for a code; the site quietly hands your session a replacement.

Reconnecting an AI assistant takes about a minute: open the connector settings, click Connect, sign in with your new password. Nothing is lost — your chats, your history and your permissions are unchanged.

Changing your password also protects your account by ending other active sessions. If you think someone else has had your password, changing it now ends every session it could have created — the website on their machine, and any AI assistant they connected — not merely their ability to sign in again. A connected AI assistant holds its own credential, so without this it would have kept working for up to two weeks after you locked them out of the login page.

If you are rotating your password routinely rather than in response to a worry, reconnecting your assistants is the only difference you will notice.

Troubleshooting

Most connection issues have been resolved. If you experience a problem, check the following:

You cannot find "Add custom connector"

• Claude Team or Enterprise: an Owner must add the connector for the organization first. Individual members cannot, and the option will not appear for them.
• ChatGPT: check you are on Pro or above, and that developer mode is switched on (Settings → Plugins → Developer mode). The feature has been called Connectors, Apps and Plugins across releases, so look under all three. On Business or Enterprise your admin may have disabled it.
• Claude Free: you are limited to one custom connector in total. If you already use one for something else, you will have to choose.

The connector is missing from Claude Desktop

Fully quit Claude Desktop and reopen it — File → Exit on Windows or Cmd+Q on macOS, not the X. The connector list appears to be read at launch, so a running app will not see one added after it started. Check under Settings → Connectors and under Customize; the location has moved between releases.

If it still does not appear, confirm it is present at claude.ai → Connectors. If it is missing there too, it was never saved and should be added again.

The web will not let me add the connector

You almost certainly added it in Claude Desktop first. The URL is then already registered to your account and the web will not accept it a second time. Remove it in Desktop, add it on claude.ai, and Desktop will pick it up again on its own.

Sign-in fails

Use the email and password that were set up for your Drill2Frac MCP access. If they are not working, contact whoever set up your account, or email Support@drill2frac.com. Include which AI assistant you were using.

Working out which account is at fault

Two separate logins are involved: your AI assistant account, and your Drill2Frac credentials. Knowing which one is refusing you saves a lot of time.

If you also use the Drill2Frac website, sign in there:

• It works there, but the connector still fails — your Drill2Frac credentials are fine, so the problem is on the AI assistant's side. Remove the connector and add it again.
• It fails there too — this is your Drill2Frac account rather than anything to do with the connector. Contact whoever set up your account, or email Support@drill2frac.com.

If the connector is your only access to Drill2Frac, there is nothing to compare against, so go straight to the same people and say what you saw.

You see fewer wells than expected

The connection shows exactly what your Drill2Frac account permits, no more and no less. If wells are missing, your access needs changing rather than anything about the connector. If you cannot see a well on the website either, the AI assistant will not see it — contact whoever set up your account, or email Support@drill2frac.com.

(The old "reports zero wells" bug, where a correctly-configured account saw an empty list, was fixed in August 2026. If you see zero wells now, it is an access question rather than that bug.)

Tool calls fail or time out

Ask again first — the AI assistant loads tool definitions on demand and a retry often clears it. If it persists, disconnect and reconnect (below).

Some FlowFX and curve queries return large amounts of data and can exceed the assistant's response limit. Narrowing the question usually fixes it: ask for a few stages rather than all of them, or a depth range rather than a whole curve. We are progressively adding filters to the endpoints where this comes up.

Checking whether the server itself is up

Open this in a browser:

https://mcp.drill2frac.ai/.well-known/openid-configuration

If you get JSON back, the server is running and the problem is on the client side. If you get nothing or an error, it is ours — contact Drill2Frac.

Reconnecting

If the connection gets into a bad state, there is no cache to clear and no processes to kill. Remove it and add it again:

1. Go to Settings → Connectors.
2. Disconnect or delete Drill2Frac MCP.
3. Add it again following Step 2.

How to use this guide

The prompts below get progressively richer. You don't have to work through them in order — pick the section that matches what you're trying to learn, copy a prompt, and try it. Replace bracketed placeholders like [well name] with a real value — use one of your own wells from the list the first prompt returns.

After each response, ask follow-ups in plain language. The conversation builds context, so you don't have to re-state which well you're working on.

Start using it: three prompts to get oriented

If you only try three things, try these — they'll give you a feel for what Drill2Frac MCP covers in about five minutes.

1. "What wells are available in Drill2Frac?"
2. "Tell me everything you know about [well name]."
3. "What FlowFX scenarios have been run on that well, and how do they compare?"

By the end of the third prompt you'll have seen well metadata, schedules, and optimized-vs-baseline FlowFX comparison — which is the headline use case for Drill2Frac.

What you can ask about

Drill2Frac MCP organizes around wells. Underneath each well are schedules (stage and cluster designs), curves (drilling/log data), and FlowFX scenarios (simulation results comparing designs). The prompts below mirror that structure.

Discovering wells

Surface what's in the system without needing to know any names.

• "What wells are available in Drill2Frac?"
• "List all the operators and how many wells each one has."
• "Show me the wells operated by [operator name]."
• "Which wells are in Reeves County?"
• "Are there other wells from the same operator within 5 miles of [well name]?"
• "Show me all the wells on the [pad name] pad."

Exploring a single well

Once you've picked a well, dig into what's known about it.

• "Tell me everything you know about [well name]."
• "Where is [well name] located? Show it on a map."
• "What's the lateral length and TD on [well name]?"
• "What schedules are available for [well name]?"
• "What curves are loaded for [well name]?"
• "What FlowFX scenarios have been run on [well name]?"

Working with schedules

This is where optimized designs get compared against geometric baselines.

• "Compare the geometric vs optimized stage schedule on [well name]."
• "Show me the cluster spacing for the Baseline schedule on [well name]."
• "What are the differences between the Baseline and PerfAct designs on [well name]?"
• "How many stages and clusters are in each design on [well name]?"
• "Plot the stage lengths for [well name]."

Working with curves

Get eyes on actual drilling and log data.

• "Show me a drilling view (GR, ROP, MSE) of [well name]."
• "What does the gamma ray look like across the lateral on [well name]?"
• "Plot the rock MSE for [well name] and tell me where the hardest rock is."
• "What curves are available on [well name], and which versions should I use?"
• "Show me the FlowFX-input curves (BREAKDOWNPRESSURE and ROCKMSE2STRESS) on [well name]."

Working with FlowFX results

The payoff prompts — optimized-design validation.

• "Compare the FlowFX results for the Baseline vs PerfAct scenarios on [well name]."
• "How does cluster efficiency change between the two designs?"
• "Which design gives the better Uniformity Index?"
• "How much slurry volume does the optimized design save vs the baseline?"
• "Why did PerfAct improve over Baseline on [well name]?"

Cross-well analysis

Once you're comfortable with one well, broaden the scope.

• "Compare the drilling curves between [well A] and [well B]."
• "Are the FlowFX gains consistent across the wells on the [pad name] pad?"
• "Which wells have the lowest mean Rock MSE?"
• "Show me how the Uniformity Index varies across all wells operated by [operator]."

Getting better answers

Don't start with a complicated question. Begin with "what wells are available" or "tell me about [well]" before jumping to multi-well comparisons. The conversational context makes follow-ups easier and more accurate.

Ask for visuals when text feels dense. "Show me on a map," "plot that," "make a chart" all work. Charts and maps are often easier to interpret than tabular output.

Be specific about which design when comparing. Drill2Frac MCP often has multiple versions of each schedule (e.g., several "Baseline" or "PERFACT_V2" entries). When asking for comparisons, specify which Baseline if you have a preference, or ask Claude to pick the canonical one and explain its choice.

Ask why a number is what it is. "Why is the MSE so high in stage 1?" or "What's driving the UI improvement?" — these prompts pull the explanation out, not just the value.

Flag data quality issues. If something looks off (a duplicate well, a noise spike in a curve, a missing field), say so. Drill2Frac MCP has known data-quality artifacts, and the conversation will produce a more accurate answer if you call them out rather than working around them silently.

Compose with other MCPs. Drill2Frac MCP gets more useful when it's not the only connector on the chat. If you've also got a financial, scheduling, or reservoir MCP enabled, ask cross-source questions: "Compare cost-per-effective-cluster across the pad," "Which scenario looks best when we factor in the rig schedule for Q3?" That cross-source composition is where this becomes most useful.

Comprehensive prompt library

A wider menu of prompts, organized by intent. Use these as starting points and adapt them to your wells and operators.

Inventory and discovery

• "How many wells does Drill2Frac MCP have access to?"
• "List the operators and counts of wells each."
• "Which wells are in [basin / county / state]?"
• "What's the most data-rich well in the system?"
• "Show me wells with FlowFX scenarios attached."
• "Show me wells with the most curves loaded."
• "Are there any duplicate or test wells I should be aware of?"

Well-level details

• "What's the API number, operator, and surface location of [well name]?"
• "What field and basin is [well name] in?"
• "What's the reference elevation on [well name]?"
• "Is [well name] tight, archived, or active?"
• "Show me [well name] on a map with its sister wells."

Schedules and design

• "List all schedules on [well name]."
• "How many stages and clusters does [schedule name] have?"
• "What are the stage lengths for [schedule name] on [well name]?"
• "Plot the stage layout for [schedule name]."
• "Show me cluster locations for [cluster schedule name]."
• "What's the cluster spacing within stage [N] of [schedule name]?"
• "Are the stages uniform length, or do they vary?"
• "How does PerfAct allocate stage lengths compared to Baseline?"

Curves and logs

• "What curves are available on [well name]?"
• "Group the curves on [well name] by category."
• "How many valid records does each curve have?"
• "Are there multiple versions of [curve name]? Which should I use?"
• "Plot [curve name] vs depth."
• "Plot GR, ROP, and MSE in a 3-track drilling view."
• "Show me the mud gas chromatography (C1/C2/C3) on [well name]."
• "Where's the highest gamma ray response on [well name]?"
• "Where's the hardest rock (highest MSE) on [well name]?"
• "Find data quality issues in the curves on [well name]."

Per-stage analysis

• "Bin the GR/ROP/MSE curves by stage for [schedule name] and show me the per-stage means."
• "Which stages have the most variable rock?"
• "Where are the toe vs heel rock differences on [well name]?"
• "Show me a per-stage bar chart of rock quality."

FlowFX scenario results

• "List the FlowFX scenarios on [well name]."
• "When was the last FlowFX run on [well name]?"
• "Compare scenarios [name A] and [name B] on [well name]."
• "What's the well Uniformity Index for [scenario]?"
• "What's the cluster efficiency for [scenario]?"
• "How does the over/under/ideal stimulation breakdown change between scenarios?"
• "How much pressure does the optimized design save?"
• "Did the optimized design pump less slurry?"
• "What scenario has the best Uniformity Index across all wells?"

Cross-well and pad comparison

• "Compare [well A] and [well B] head-to-head."
• "What's the closest well to [well name]?"
• "Show me the [pad name] pad on a map."
• "Are completion designs consistent across the pad?"
• "Which well on the pad has the best FlowFX outcome?"
• "How does rock MSE compare across the pad?"

Diagnostic and troubleshooting

• "Test my connection to Drill2Frac."
• "How long does it take to load curve data for [well name]?"
• "What's the largest data payload available on [well name]?"
• "Are there any wells with missing surface coordinates?"
• "Are there any duplicate well records I should clean up?"
• "What endpoints are not yet exposed in the MCP layer?"

Glossary

• API / UWI — Unique Well Identifier. The 14-digit number assigned to each wellbore by the regulatory agency.
• MD — Measured Depth. Distance along the wellbore path, in feet.
• TVD — True Vertical Depth. Vertical distance from surface to a point in the wellbore.
• GR — Gamma Ray. Natural radioactivity log used to identify lithology; high GR usually indicates shale.
• ROP — Rate of Penetration. How fast the bit is drilling, in ft/hr.
• MSE — Mechanical Specific Energy. Energy required to remove a unit volume of rock, in psi. Higher MSE = harder rock.
• Stage — A section of the lateral isolated for a single frac treatment.
• Cluster — A group of perforations within a stage where fluid enters the formation. A typical stage has 5–10 clusters.
• Geometric (Baseline) design — Equal stage lengths and equal cluster spacing, ignoring rock variability.
• Optimized (PerfAct/PERFACT) design — Stage and cluster placement that responds to rock properties (MSE, stress, gamma).
• UI / Uniformity Index — A FlowFX metric (0–1) measuring how evenly fluid distributes across all clusters. Higher is better.
• Cluster Efficiency — Percentage of clusters that received the intended stimulation (neither over- nor under-stimulated).
• FlowFX — The hydraulic-fracturing simulation engine that scores completion designs.