Developers

Quickstart

Connect an assistant to a Production Engine workspace in a few minutes. You need to be a workspace owner or admin, on an active plan or free trial.

Claude

  1. Open Production Engine in Claude's connector directory and click Connect.
  2. Sign in to Production Engine and click Allow. When Claude asks for estimates, the approval screen says so.

To add it by hand instead, open Settings, then Connectors, then Add custom connector in Claude, and enter the address below.

Connector address
https://production-engine.com/api/mcp

Claude discovers the sign-in page on its own from the server's OAuth metadata. See OAuth 2.1 for the flow it runs.

ChatGPT

ChatGPT needs Developer mode turned on to add a connector. Add Production Engine with the same address, then sign in and click Allow.

Connector address
https://production-engine.com/api/mcp

A ChatGPT connection is always read-only and sees a smaller tool set: no bank feed, Saturation or estimate tools. The MCP reference lists which tools it gets.

Claude Code and other token clients

  1. In Production Engine, open Company Settings, then Integrations.
  2. Under API tokens for developers, name a token and create it.
  3. Copy the token. It is shown once and starts with pe_.
  4. Add the server with the token as a bearer header.
Terminal
claude mcp add --transport http production-engine https://production-engine.com/api/mcp \
  --header "Authorization: Bearer pe_exampleEXAMPLEexampleEXAMPLEexampleEXAMPLE0"

Any MCP client that supports Streamable HTTP with a custom Authorization header works the same way. Tokens are read-only. See API tokens.

Make your first call

The server takes one JSON-RPC 2.0 message per POST and answers with JSON. With a token in PE_TOKEN, ask who the token acts as:

curl
curl https://production-engine.com/api/mcp \
  -H "Authorization: Bearer $PE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "whoami", "arguments": {} }
  }'
Response
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [{ "type": "text", "text": "{ \"workspace\": { ... } }" }],
    "structuredContent": {
      "workspace": { "id": "cmexampletenant000000001", "name": "Example Studio" },
      "member": { "email": "producer@example.com", "role": "OWNER" },
      "access": "read"
    },
    "isError": false
  }
}

Then list the tools this connection can call:

curl
curl https://production-engine.com/api/mcp \
  -H "Authorization: Bearer $PE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/list" }'

Every tool, its input schema and an example result are in the MCP server reference.

Disconnect

In Production Engine, open Company Settings, then Integrations. Click Disconnect next to an assistant connection, or Revoke next to an API token. Both stop working on the next call.