Claude and ChatGPT integration for field operations

What you can do with it

Once connected, your AI app can read your PIEBENCH data and, if you allow it, act on it. A few things people ask:

• "Which work orders in the Riverbend project are past their due date, and how far behind is each crew?"
• "Who are the team leads for those crews? Draft a polite follow-up to each one."
• "What's waiting in my approval queue? Approve the ones with a photo and a serial."
• "How did each team do on attendance last week?"
• "Show me the last week of sync runs with our billing system. Did anything fail?"

The AI app does the looking up, and you stay in charge of anything that changes data.

Connect it

Every app needs the same server address:

https://mcp.piebench.com/mcp

Claude (web, desktop and mobile). Go to Settings → Connectors, choose to add a custom connector, paste the address and connect. A PIEBENCH sign-in page opens: log in, tick what Claude may do, and approve. In a chat, turn PIEBENCH on from the tools menu.

ChatGPT. In ChatGPT's settings, open Apps & Connectors and turn on developer mode in the advanced settings. Create a new connector with the same address and sign in with PIEBENCH when asked. Developer mode is only available on some ChatGPT plans.

Claude Code. Run claude mcp add --transport http piebench https://mcp.piebench.com/mcp, then type /mcp in Claude Code, pick piebench and authenticate.

Other MCP apps. Any app that supports remote MCP servers with OAuth sign-in can connect with the same address.

You don't need to set anything up in PIEBENCH first. If you don't have an account yet, the sign-in page lets you create one.

You choose what it can do

When you connect, PIEBENCH shows a consent screen with one row per area of the product, and two choices for each: View and Make changes. Viewing is ticked by default; making changes is not. The app only gets what you tick, and it never gets more than your own role allows. A field agent who can't see the users list in PIEBENCH can't give an AI app access to it either.

There are no tools for deleting anything, billing, or managing users and roles.

In Claude, every action that changes data asks you to confirm before it runs.

See and revoke connections

In PIEBENCH, go to Settings → AI Apps. You'll see each connected app, the site it signs in through, when it was connected and last used, and exactly what it may do. Disconnect removes access straight away. Tenant admins see every connection in the account.

To change what an app may do, disconnect it and connect again; the consent screen comes back with fresh choices.

Security

• Sign-in uses OAuth 2.1 with PKCE. The AI app never sees your PIEBENCH password.
• Access tokens last an hour and refresh tokens are replaced every time they're used. Both are stored hashed.
• Every request is checked against your account, so an app connected to one organisation can never reach another's data.
• Plan limits apply exactly as they do in the console.
• Data a tool returns goes to the AI app you connected, under that app's own terms. Only connect apps your organisation is happy to share that data with.

How PIEBENCH fits

The MCP server sits on top of the same platform your teams already use: the offline field app, no-code workflows and integrations with billing and HES systems. See smart meter field operations for the full picture.