MCP Server (AI agents)

Caledee exposes a Model Context Protocol server so AI agents like Claude Desktop can manage your bookings, event types, and availability using natural language.

The MCP server is part of the Team plan. Tokens issued on a Free or Pro plan won’t authenticate against it.

Quick start

Create an OAuth app at Settings → Developers (or use the one created at signup).
Authorize via the OAuth 2.0 flow to get an access token (see the OAuth 2.0 docs).
Point your MCP client to https://caledee.com/api/mcp with the Bearer token.

Claude Desktop configuration

In your Claude Desktop MCP settings, add:

{
  "mcpServers": {
    "caledee": {
      "url": "https://caledee.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-access-token>"
      }
    }
  }
}

Available tools

Tool	Description
list_bookings	List upcoming, past, or canceled bookings
get_booking	Get full details of a booking
cancel_booking	Cancel a booking (invitee is notified)
list_event_types	List your event types and settings
create_event_type	Create a new event type
update_event_type	Update name, duration, or status
list_schedules	View availability schedules and rules
get_stats	Booking statistics and no-show rate
list_leads	View captured leads
get_booking_link	Get the public URL for an event type
reschedule_booking	Move a booking to a new time (invitee notified, calendars updated)
create_availability_override	Set custom hours or close a single day
set_out_of_office	Block a date range so nobody can book you

Write tools (cancel, reschedule, create / update event types, availability overrides, out-of-office) require a token granted the matching write scope. A read-only token only gets the read tools.

Example conversations

“Show me my bookings for this week”
“Cancel the meeting with Jean tomorrow”
“Create a 45-minute Demo event type”
“What’s my no-show rate this month?”
“Send me the booking link for my consultation”
“Move my 2pm with Jean to Thursday at 10am”
“I’m off next Monday — block it”
“Set me out of office June 20th to July 5th”

Authentication

The MCP endpoint requires an OAuth 2.0 Bearer token. See the OAuth 2.0 docs for the full authorization flow. All tools are scoped to the authenticated user — no cross-user access is possible.

Protocol

The server implements Streamable HTTP (the latest MCP transport). It runs stateless — each request creates a fresh server instance authenticated to the token’s user. Compatible with Claude Desktop, Claude Code, and any MCP client that supports Streamable HTTP.