Connect to the Petroleum Office MCP Server

Step-by-step setup instructions for connecting your AI assistant to Petroleum Office. Once connected, the assistant gains access to the full function catalog, all blueprints, and theory documentation.

Server endpoint

https://mcp.petroleumoffice.com/

When you add the server in your client, you'll be prompted to sign in with your Petroleum Office account through a standard OAuth flow. No tokens or API keys to manage.

Permissions the connection asks for

Part way through the sign-in, your client shows a permissions screen. The server accepts two scopes, and only two:

Between them they let the server tell which account is calling, so your licence and your rate limits resolve to you. They cover identity and nothing else: no access to your mailbox, no access to files or workbooks on your machine, and no ability to change your Petroleum Office account.

If your client offers more than these two, clear the rest before connecting — a request for scopes the server doesn't accept is rejected, and the connection fails. Grok pre-selects five; see the Grok steps below.

OAuth details (for clients that need manual config)

Most clients (claude.ai, Claude desktop, Claude for Excel, Grok) handle the OAuth flow automatically — you only enter the server URL above. For clients that require manual OAuth configuration, the parameters are:

Adding to Claude

The same connector configuration covers claude.ai web, the Claude desktop app, and Claude for Excel — Anthropic propagates custom connectors across all your Claude surfaces.

1. Open claude.ai (or the Claude desktop app).
2. Go to Settings → Connectors.
3. Click Add custom connector.
4. Enter the server URL: https://mcp.petroleumoffice.com/
5. Sign in with your Petroleum Office account when prompted.
6. Approve the permissions screen. Claude asks for email and profile — the two the server accepts — so there is nothing to change here.
7. The connector is now active across all your Claude surfaces.

After connecting, the Petroleum Office tools become available in any new Claude conversation. In Claude for Excel, the tools fire automatically when the agent needs petroleum engineering context.

First prompts to try

• "Calculate bubble-point pressure with Standing's correlation: API 35, gas gravity 0.75, GOR 600 scf/STB, 180 °F."
• "Build me a small PVT package workbook for a black-oil reservoir at 4,500 psia, 220 °F."
• "Search Petroleum Office blueprints for decline curve analysis examples."

Adding to Grok

MCP support in Grok is newer and the menu paths vary by plan. The general flow:

1. Open grok.com and sign in.
2. Navigate to Settings → Connectors (or Integrations → MCP servers depending on your plan).
3. Add a new MCP server with URL: https://mcp.petroleumoffice.com/
4. Cut the scope list down to email and profile. Grok pre-selects five — openid, profile, email, public_metadata and private_metadata — and connecting with all five fails. Remove openid, public_metadata and private_metadata, leaving the two the server accepts.
5. Complete the OAuth sign-in flow with your Petroleum Office account.
6. Grant the connection — Petroleum Office tools become available in chat.

Step 4 is Grok-specific, and it isn't something you've configured wrongly. Grok builds that list from the sign-in provider, which publishes every scope it supports across every application, rather than from the two this server declares for itself. Claude reads the server's own list and asks for the right pair, which is why the step appears here and not above.

Grok works best as a research and screening surface today — catalog browse, theory doc lookup, comparing methods. As Grok's MCP support matures, calculation and artifact workflows will expand.

Other clients

We've verified the flows above end-to-end. As we test additional clients (Cursor, VS Code with Copilot, Windsurf, ChatGPT) we'll publish their setup paths here.

For now, any client that supports remote MCP servers can connect via:

npx mcp-remote https://mcp.petroleumoffice.com/

This wraps the remote server as a local MCP transport.

Troubleshooting

The connection fails when you approve the permissions screen

• Too many scopes were requested. The server accepts email and profile only, and a request carrying openid, public_metadata or private_metadata is rejected.
• In Grok, all five are selected for you — remove the three extras and connect again.
• If your client doesn't let you edit the list, configure it manually with the scopes in the OAuth details table above.

OAuth flow doesn't open or fails to redirect

• Make sure pop-ups aren't blocked for petroleumoffice.com.
• Sign in to your Petroleum Office account first at petroleumoffice.com, then retry the connector setup.

Tools don't appear after connecting

• Start a fresh conversation in your client — existing conversations don't always pick up newly-added connectors.
• Verify the connector is listed and enabled in your client's connector settings.

Calculations return errors

• Each tool documents its expected inputs. Ask the assistant to "show the parameter signature for functions_calc" — it will pull the catalog entry directly.