Connecting Claude

Connect Claude Desktop, Claude Code or claude.ai to the PetroBench MCP server and run your first prompts against your wells.

When you finish, Claude lists PetroBench tools such as find-wells and get-simulation, and answers questions about your own wells with the same permissions your login has.

Prerequisites

  • API access enabled for your organization. The Connected apps tab under Settings is visible when it is.
  • Claude Desktop, Claude Code, or a claude.ai plan that allows custom connectors.

Connect Claude Desktop

  1. In PetroBench, open SettingsConnected apps.
  2. Select Claude Desktop. The dialog shows the server URL and the steps.
  3. Copy the URL:
MCP endpoint
https://app.petrobench.com/mcp
  1. In Claude Desktop, open SettingsConnectorsAdd custom connector and paste the URL.
  2. Select Connect and approve the consent screen in your browser.

The same steps apply on claude.ai under SettingsConnectors. No config file and no Node.js are needed.

Connect Claude Code

  1. In PetroBench, select Claude Code under Connected apps and copy the command.
  2. Run it in any terminal where the Claude Code CLI is installed:
claude mcp add --transport http petrobench https://app.petrobench.com/mcp
  1. Run /mcp inside Claude Code and pick Authenticate. The same consent screen opens.

Add --scope user to the command to make the server available in every project on the machine.

Use a token instead of OAuth

For a client that cannot complete OAuth, or for an agent that runs on a schedule, create a token under SettingsAPI tokens and send it as a Bearer credential. Grant only the abilities the agent needs.

  • Personal access token: carries your own permissions. Right for trying this out.
  • Service token: owned by a division, survives offboarding. Right for a shared or scheduled agent.

See Authentication for token creation and scopes.

What to check

  • Claude's tool list shows PetroBench tools.
  • A question about a named well returns your data, not a refusal.
  • The authorization appears under Connected apps with its scopes and last used time.

Tools missing: the consent or token is short an ability. Reconnect and approve the scopes you need. Sign-in loops: disconnect the app under Connected apps, add it again, and complete consent in the same browser session.

Sur cette page