Use Your Rod-Lift Wells in VS Code
Add PetroBench as an HTTP server. VS Code can then find wells, read equipment, and run RodSim simulations with the permissions you already have.
| Cases | |
|---|---|
| Inside all limits | 1,038 |
| Over gearbox limit | 111 |
| Over rod loading limit | 52 |
| Under rod min stress | 20 |
| 2.0 in | 1.75 in | 1.5 in | |
|---|---|---|---|
| Stroke rate | 5.6 SPM | 7.1 SPM | 9.2 SPM |
| Fluid rate | 200 bfpd | 200 bfpd | 200 bfpd |
| Gearbox load | 96% | 86% | 84% |
| Max rod stress | 88% | 81% | 78% |
| System efficiency | 33% | 31% | 27% |
| Base | Case B | |
|---|---|---|
| Stroke rate | 5.0 SPM | 4.0 SPM |
| Gearbox load | 94% | 78% |
| Pump fillage | 71% | 88% |
| Max rod stress | 82% | 76% |
| Oil rate | 157 bopd | 155 bopd |
| 1.0 in | 7/8 in | |
|---|---|---|
| Top taper stress | 71% | 86% |
| Rod string weight | 9,850 lb | 8,420 lb |
| Gearbox load | 83% | 79% |
| Fatigue check | Pass | Marginal |
| 4.0 SPM | 5.0 SPM | 6.0 SPM | |
|---|---|---|---|
| Oil rate | 118 bopd | 131 bopd | 136 bopd |
| Pump fillage | 96% | 89% | 74% |
| Gearbox load | 71% | 86% | 98% |
- Peak load
- 29.2 klb
- Min load
- 8.5 klb
- Fillage
- 71%
- Net stroke
- 113 in
- Peak load
- 29.2 klb
- Min load
- 8.5 klb
- Fillage
- 68%
- Net stroke
- 108 in
Connect VS Code in Two Steps
Run MCP: Add Server from the Command Palette, or add the config yourself.
MCP access is off by default. Your PetroBench account team turns it on for your organization.
- 1
Add the config
mcp.json{ "servers": { "petrobench": { "type": "http", "url": "https://app.petrobench.com/mcp" } } } - 2
Sign in to PetroBench
Accept the trust prompt and sign in when VS Code asks.
Try These on Your Wells
Start by asking VS Code to list your wells. If it returns wells from your organization, the connection works. Then pick a job below.
See All PromptsThe same prompts work in
VS Code and PetroBench
PERM-4821 shuts down on gearbox overload alarms. What is the root cause?
-
get-well -
validate-well-data -
get-well-production
Peak torque is at 94% of the gearbox rating at 5.0 SPM. The last fluid shot puts pump fillage at 71%, and the card shows fluid pound on the downstroke.
- Peak load
- 29.2 klb
- Min load
- 8.5 klb
- Fillage
- 71%
- Net stroke
- 113 in
VS Code and PetroBench
PERM-4821 is having its rods pulled for offset frac protection. Based on last month's average production, use RodSim to see if we can downsize the pump to 1.75 in or 1.5 in.
-
get-well-production -
execute-simulation -
compare-simulations
Both sizes make the 200 bfpd target. The 1.75 in pump drops gearbox load from 96% to 86% at 7.1 SPM. The 1.5 in pump needs 9.2 SPM and gains little, so 1.75 in fits best.
| 2.0 in | 1.75 in | 1.5 in | |
|---|---|---|---|
| Stroke rate | 5.6 SPM | 7.1 SPM | 9.2 SPM |
| Fluid rate | 200 bfpd | 200 bfpd | 200 bfpd |
| Gearbox load | 96% | 86% | 84% |
| Max rod stress | 88% | 81% | 78% |
| System efficiency | 33% | 31% | 27% |
VS Code and PetroBench
Run RodSim Dynamics on PERM-3304. Which operating conditions stay inside the limits?
-
execute-simulation -
poll-job -
get-simulation-results
1,038 of 1,221 cases stay inside the limits. Gearbox load causes most failures, above 5.5 SPM at low pump intake pressure.
| Cases | |
|---|---|
| Inside all limits | 1,038 |
| Over gearbox limit | 111 |
| Over rod loading limit | 52 |
| Under rod min stress | 20 |
VS Code and PetroBench
Which of my wells run closest to their gearbox limit?
-
fleet-wells
PERM-4821 and PERM-1190 run closest to their limits. PERM-3304 is third at 86%.
You Decide What VS Code Can Do
You pick the permissions when you connect. VS Code only sees tools that match them and your role.
Every call is recorded with your user and token. Disconnect at any time under Settings > Connected Apps.
Authorize VS Code
Permissions for VS Code
- Read wells and equipment
wells:read - Read simulations and results
simulations:read - Run simulations
simulations:run - Change wells and equipment
wells:write
Connecting VS Code
Short answers for engineers and IT.
No. VS Code signs in with OAuth. You approve the connection on the PetroBench consent screen in your browser.
No. MCP access is off by default. Your PetroBench account team turns it on when your organization asks.
Only what your role and the approved scopes allow, inside your organization. Without write scopes, VS Code never sees write tools.
Only with write scopes that you tick when you connect. AI clients can make mistakes, so review any change before you confirm it, and keep write access to the users who need it.
Open Settings > Connected Apps in PetroBench and disconnect it. To change scopes, disconnect and connect again.
More questions? Contact Us
Connect Another AI Tool
Every tool uses the same server URL and the same PetroBench sign-in.
https://app.petrobench.com/mcp Using another tool? Paste this URL into any MCP client that supports remote servers and OAuth.
Assistants
- Claude Add PetroBench as a custom connector.
- ChatGPT Add PetroBench as a custom app.
- Gemini Add PetroBench as a custom app.
- Grok Add PetroBench as a custom connector.
- Copilot Add PetroBench to a Copilot Studio agent.
- Perplexity Add PetroBench as a custom remote connector.
- Mistral Vibe Add PetroBench as a custom MCP connector.
Coding agents
-
Claude Code Add PetroBench from your terminal. -
Codex Add PetroBench to your Codex config. -
Cursor Add PetroBench to your MCP config. -
Devin Add PetroBench as a custom MCP. -
Antigravity Add PetroBench to your MCP config. -
Muse Code Add PetroBench to your Muse Code settings. -
Kiro Add PetroBench to your Kiro MCP config. - Grok Build Add PetroBench from your terminal.
- Grok Bot Ask Grok Bot to add PetroBench as a custom server.
-
OpenClaw Add PetroBench from your terminal. -
OpenCode Add PetroBench to your OpenCode config. -
Zed Add PetroBench as a remote server in Zed. -
Factory Droid Add PetroBench from your terminal. -
Cline Add PetroBench with the Cline CLI. -
Warp Paste the PetroBench config into Warp. - Devin Desktop Add PetroBench to your MCP config.
Use VS Code on Your Own Wells
Your PetroBench account team turns on MCP access for your organization. Then ask your first question in plain words.