Developers
Your Ready account, in Claude, ChatGPT or your own tools
One key from Settings → Developers. Read tools return your live invoices, jobs, customers, quotes and open times. The two write tools make drafts in your approval inbox; nothing goes to a customer without your tap.
1. Make a key
In the Ready app: Settings → Developers → Create key. Give it a name (“Claude Desktop”). Tick Can draft only if you want that tool to be able to draft quotes and messages. Copy the key once; it isn’t shown again.
2. Connect Claude
Claude.ai (web and mobile): Settings → Connectors → Add custom connector → name Ready, URL https://prontco.ca/api/ready-mcp, and paste the key when it asks. Then ask Claude “who owes me money?”.
Claude Desktop / Claude Code: add this to your MCP config:
{
"mcpServers": {
"ready": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://prontco.ca/api/ready-mcp",
"--header", "Authorization: Bearer rk_YOUR_KEY"]
}
}
}
3. Connect ChatGPT
ChatGPT → Settings → Connectors (or a custom GPT’s Actions) → add an MCP server with the same URL and Authorization: Bearer rk_YOUR_KEY. Developer mode may be required on your plan.
What the tools can do
| Tool | Needs | Does |
|---|---|---|
whoami | read | Your business, trades, areas, plan |
list_owed_invoices | read | Sent, unpaid invoices with who owes what |
list_jobs · list_customers · list_quotes | read | Your board, filtered |
get_calendar | read | Open times, same as your booking page |
create_draft_quote | read+write | A quote draft in your inbox. You approve, then it’s emailed. |
create_draft_message | read+write | An email or text draft in your inbox. You approve, then it sends. |
There is no tool that sends anything. That is on purpose.
Plain REST, if you’d rather
GET https://prontco.ca/api/ready-mcp?rest=invoices (also jobs, customers, quotes, calendar) with the same Authorization: Bearer header. JSON back.
Webhooks
Settings → Developers → Add webhook: an https URL on your server and the events you want: job.created, invoice.paid, quote.accepted, doc.expiring. Each delivery is a JSON POST with headers X-Ready-Event, X-Ready-Delivery and X-Ready-Signature: sha256=<HMAC of the body with your signing secret>. Failed deliveries retry up to five times over about two hours. The “Test” button sends a job.created with test: true.
Limits and safety
- Keys are per account and can be revoked any time; every use is stamped.
- Read tools return at most 200 rows per call.
- Customer data you pull into another tool is covered by your own privacy obligations (PIPEDA / BC PIPA).
- The API is switched on per account; if it isn’t on yours yet, ask in Help.