One key. Your customers, invoices, projects and tickets.
A REST API for your own scripts and integrations, and an MCP server so an AI assistant — Claude Desktop, or any other client that speaks MCP — can read and work with the same records, through the same key.
The assistant can do exactly what the key can do
An MCP tool is a thin wrapper over the identical REST operation, checked against the identical scopes on the identical key. Give a key read-only access to customers and invoices, and an assistant connected with it can look those up and nothing more — it cannot quietly gain an ability the key itself was never granted.
What you can reach today
Your own details, customers, contacts, invoices and projects, all readable; creating an invoice is the one write available so far, always priced from its own line items — a total can never be handed to it directly. More of the product reaches the API as it is built, on the same key, with nothing to reconfigure when it does.
Create a key in Setup
Choose its scopes, copy it once, and point either the REST base URL or the MCP endpoint at it. Revoking the key closes both doors at the same moment.