MCP setup

Each deployment runs an MCP server that offers the Booking API’s operations as tools:

https://<tenant>.kwickbooking.com/mcp

kwickbooking.com is a placeholder: use the base URL the venue’s admin gives you with your key, as described in Your base URL.

• Transport: Streamable HTTP, stateless. There is no session to keep.
• Authentication: your integration key as Authorization: Bearer kb_ik_live_… on every request.

Claude Code

claude mcp add --transport http kwickblocks https://<tenant>.kwickbooking.com/mcp \
  --header "Authorization: Bearer kb_ik_sandbox_…"

Run /mcp in Claude Code to check the server is connected and see its tools.

Voice and chat agent platforms

Agent platforms that support remote MCP servers (for example ElevenLabs agents) need:

• the server URL, https://<tenant>.kwickbooking.com/mcp;
• the transport, Streamable HTTP;
• one request header, Authorization with the value Bearer kb_ik_live_….

Give each agent its own key, so the venue’s bookings record the right channel and the key can be rotated or revoked on its own.

Other clients

Any MCP client that speaks Streamable HTTP and can send a custom header works. Point it at the URL above with the Authorization header.

What you get

• Tools follow the key. The tool list contains only the tools your key’s capabilities allow, and only those the deployment’s features include. See the tool reference.
• Every result has a summary that an agent can read to a guest as it is, alongside structured content.
• Errors arrive as tool errors whose text is the same problem JSON as the REST API, with a detail that is safe to read out.
• Retries are safe. Tools that write accept an optional idempotencyKey; without one, an identical call within 10 minutes returns the first answer.
• Destructive tools say so. cancel_booking is marked destructive; confirm with the guest before calling it.