Conectar o Claude
Conecte o Claude Desktop, o Claude Code ou o claude.ai ao servidor MCP da PetroBench e execute os primeiros comandos sobre os seus poços.
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.
Pré-requisitos
- 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.
Conectar o Claude Desktop
- In PetroBench, open Settings → Connected apps.
- Select Claude Desktop. The dialog shows the server URL and the steps.
- Copy the URL:
https://app.petrobench.com/mcp- In Claude Desktop, open Settings → Connectors → Add custom connector and paste the URL.
- Select Connect and approve the consent screen in your browser.
The same steps apply on claude.ai under Settings → Connectors. No config file and no Node.js are needed.
Conectar o Claude Code
- In PetroBench, select Claude Code under Connected apps and copy the command.
- Run it in any terminal where the Claude Code CLI is installed:
claude mcp add --transport http petrobench https://app.petrobench.com/mcp
- Run
/mcpinside 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.
Usar um token em vez de OAuth
For a client that cannot complete OAuth, or for an agent that runs on a schedule, create a token under Settings → API 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.
O que verificar
- 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.