Setup
- Create a named key under Settings → Integrations → Agents & MCP. It is shown once.
- Store the full key in
BOOKINGBREEZE_AGENT_KEYor your client's protected credential store — never in a prompt or chat message. - Add this MCP configuration:
{
"mcpServers": {
"bookingbreeze": {
"url": "https://app.bookingbreeze.io/mcp",
"headers": { "Authorization": "Bearer ${env:BOOKINGBREEZE_AGENT_KEY}" }
}
}
}Check it worked
Start a new agent conversation and send:
Run the BookingBreeze checkin tool with agent_id: "cursor". Tell me if BookingBreeze is connected and ready. If not, tell me what failed.
A successful check-in names your BookingBreeze account, operator role, and read-only or read + draft access.
Example prompts
What accommodation and activity availability do we have next week?List bookings arriving in the next 14 days and group them by payment status.Show our active and draft rate rules for the beachfront bungalow.Draft a high-season nightly rate of IDR 1,750,000 for August 1–31, every day, and let me review it.Create an unpublished activity draft for a 90-minute sunset surf session and let me review it.List our unpublished catalog items and draft rate rules that still need operator review.Troubleshooting
The client says authentication failed. Confirm the complete key starts with bbz_, is stored in the client credential rather than a prompt, and has not been revoked.
The agent can read but cannot create a draft. The key is read-only, the operator is staff, or the record is already published. An account admin must create a read + draft key.
A draft update says it changed. Read the draft again and retry with its latest lock version. BookingBreeze rejects stale agent updates.
A create timed out. Retry with the same idempotency key. BookingBreeze returns the same draft instead of creating another.
Nothing goes live automatically
Agent writes create non-live drafts. Publication and every consequential action remain in the authenticated BookingBreeze backoffice.