MCP server

Cooledge runs a remote MCP (Model Context Protocol) server so AI assistants can work with your business data directly. Claude, Cursor, ChatGPT and any other MCP-capable client can search customers, check the calendar, create jobs, draft quotes and more, always within the permissions you grant.

The server lives at:

https://app.cooledge.com.au/api/mcp/mcp

It speaks the Streamable HTTP transport. Every tool call runs through the same permission scopes, plan checks and rate limits as the REST API.

Connect with OAuth (recommended)

Most MCP clients connect with one click. Add the server URL and the client walks you through it:

Add a custom connector or MCP server in your client and paste the server URL above.
Your browser opens a Cooledge consent screen. Sign in if you are not already.
Review what the app is asking for and choose Allow access.
The client finishes the connection automatically. You are done.

Client specifics:

Claude (claude.ai and Claude Desktop): Settings, then Connectors, then "Add custom connector". Paste the server URL.
Cursor: add the server under MCP settings with the URL above and follow the sign-in prompt.
ChatGPT: add Cooledge as a connector in settings where MCP connectors are supported on your plan.

Behind the scenes the client registers itself, sends you to https://app.cooledge.com.au/oauth/authorize for consent and exchanges a one-time code for tokens. Access tokens rotate automatically, so a connection keeps working for as long as you leave it connected and use it at least every 30 days.

Connect with an API key

Clients that do not support OAuth can authenticate with an API key from Settings, then Developers. Configure the client to send it on every request, either as a bearer token or in the X-Api-Key header:

Authorization: Bearer ck_live_AB12CD_your_secret_here

Key-based connections have the same abilities as OAuth connections. The difference is lifecycle: keys live until you revoke them, while OAuth connections can be disconnected per app.

What the assistant can do

The server exposes 25 tools over your Cooledge data. Reads cover business context, the calendar, customers, jobs, quotes, invoices, bookings, leads and overdue invoices. Writes cover creating and updating customers, sites, jobs, bookings and leads, creating ducted quotes, adding invoice lines and sending quotes and invoices.

Every tool respects the scopes on the credential. An OAuth consent screen lists the scopes an app asked for. If you approve a narrower list, tools outside it return a permission error the assistant can read and explain.

Disconnect an app

Go to Settings, then Developers, then Connected apps. Every active OAuth connection shows the app name, who approved it, its scopes and when it was last used. Disconnect cuts off access immediately. The app can reconnect later only by going through consent again.

Errors and limits

MCP tool calls share the platform limits: 120 requests per minute per credential by default. Rate limit, permission and validation problems come back inside the tool result so the assistant can adjust and retry sensibly. If your plan does not include API access, tool calls explain that too.