Developers
Build on Production Engine
Production Engine exposes a workspace to AI assistants and other software through a Model Context Protocol server, OAuth 2.1 sign-in, workspace API tokens and signed webhooks.
What you can build with
| Surface | What it does | Direction |
|---|---|---|
| MCP server | Answers questions about projects, budgets, shoot days, crew, deliverables, invoices and the pipeline. One tool can start an AI estimate. | Your client calls Production Engine |
| OAuth 2.1 | Lets a person connect an assistant by signing in and clicking Allow. PKCE and dynamic client registration. | Your client calls Production Engine |
| API tokens | A workspace token for MCP clients that take a header instead of a sign-in, such as Claude Code. | Your client calls Production Engine |
| Webhooks | A signed JSON POST when an invoice is paid, an estimate is accepted, a project is created, a call sheet is sent or a bank alert fires. | Production Engine calls you |
Assistants read workspace data through the MCP server at https://production-engine.com/api/mcp, which speaks JSON-RPC 2.0 over HTTPS. Other software reads it through the REST API at https://production-engine.com/api/v1 with a scoped token.
How access works
- Every connection acts as one workspace owner or admin. Their membership and role are checked again on every call, so removing them or lowering their role ends their connections at once.
- Connections need the workspace's plan in good standing: active, trialing, or past due within the grace period.
- Tools only read, with one exception:
start_estimate, offered only when the person approved estimates while connecting. - Money is integer cents in
amount, with a formatteddisplaystring beside it. - Only SHA-256 hashes of tokens and authorization codes are stored.
Documentation
- QuickstartConnect Claude, ChatGPT or Claude Code to a Production Engine workspace and make your first MCP call.
- AuthenticationWorkspace API tokens, OAuth 2.1 with PKCE and dynamic client registration, scopes, token lifetimes and refresh rotation.
- MCP serverThe Model Context Protocol server at /api/mcp: transport, methods and every tool with its input schema, an example call and the result shape.
- WebhooksSigned JSON events for paid invoices, accepted estimates, projects, deliverables, review notes, shoot days, sent call sheets and bank alerts, with verification code and the retry schedule.
- HTTP endpointsEvery public endpoint a developer calls: the MCP server, OAuth discovery, client registration and the token endpoint.
- Errors and limitsJSON-RPC error codes, tool errors, OAuth errors, HTTP statuses, request size caps and the rate limits on the OAuth endpoints.
- SupportHow to reach the Production Engine team about an integration.
- REST APIRead a workspace's projects, shoot days, deliverables, clients, contacts, locations, crew and media drives, and write projects, deliverables, cuts, review notes and external links, over HTTPS with a scoped API token.