Skip to content

The scheduling MCP server

Connect an MCP-capable AI assistant to Artibox Calendar. It finds slots and manages bookings, with exactly your token's rights.

The Artibox Calendar scheduling MCP server follows the Model Context Protocol (revision 2025-06-18, Streamable HTTP, JSON-RPC 2.0).

  • Endpoint: POST https://your-application-domain/api/v1/mcp
  • Header: x-api-key with a personal token (rdv_pat_…) or an OAuth access token (rdv_oat_…).
  • Stateless: one JSON-RPC message per request; GET and DELETE answer 405. Same 100 calls a minute as any /api/v1 call.

Current limitation: clients that only send Authorization: Bearer … after their own MCP OAuth flow are not supported yet. Use a client that can send x-api-key, or a bridge such as mcp-remote.

Tools

  • list_event_types (types:lire): your active event types.
  • find_available_slots (types:lire): free slots of a type, 7 days by default, 62 at most.
  • book_meeting (reservations:ecrire): books a slot; the guest gets the confirmation.
  • list_bookings (reservations:lire): visible bookings, 30 days by default, first 50.
  • cancel_booking (reservations:ecrire) and reschedule_booking (reservations:ecrire).

A tool outside the token's scopes is not listed by tools/list.

Connect to the scheduling MCP server

claude mcp add --transport http artibox-calendar https://your-application-domain/api/v1/mcp \
  --header "x-api-key: rdv_pat_…"
{
  "mcpServers": {
    "artibox-calendar": {
      "url": "https://your-application-domain/api/v1/mcp",
      "headers": { "x-api-key": "rdv_pat_…" }
    }
  }
}

Create the token as in the quick start, with only the scopes you need. Other integration options are on the developers page and in the API reference.

Connect your assistant

Create your account, then a token with the scopes you choose.

Create my account