Skip to main content
The Cal ID MCP server lets an AI assistant work with your Cal ID account directly. Once connected, you can ask your assistant to check bookings, find open slots, create event types, or update contacts — in plain language, without opening the dashboard or writing any code. Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. Cal ID runs a hosted MCP server, so there is nothing to install or self-host — you point your assistant at a URL and authenticate with your API key.
Server URL: https://mcp.cal.id/mcpReady to set it up? Go straight to Connect your AI assistant.

​
What you can do

Bookings

Ask what’s coming up, filter by attendee or date, reschedule a meeting, or cancel one.

Availability

Find open slots, review and edit weekly schedules, and reserve a slot before confirming.

Event types

List, create, update, and delete event types for yourself or a team.

Contacts & teams

Search contacts, review meeting history, and manage team members and team events.

​
Prompts to try

Once connected, these all work without naming a single tool:
  • “What bookings do I have this week?”
  • “Show my available slots for next Monday.”
  • “Create a 30-minute sales demo event type.”
  • “List my contacts and show the recent meeting history for one of them.”
  • “Reschedule my 3pm on Thursday to Friday morning.”
You rarely need to name tools yourself. Describe the outcome you want and let the assistant choose. Tool names are only useful when you’re debugging — see the tool reference.

​
What you need

  • An MCP-compatible app — Claude Desktop, Claude web connectors, Cursor, ChatGPT connectors, or any client that supports remote MCP servers.
  • A Cal ID API key. Generate one at Settings → Developer → API Keys, or follow How to get your API key.

​
How access and permissions work

The MCP server acts as you. It uses your API key, so an assistant connected to it can see and change anything your own account can see and change — and nothing beyond it.
There is no read-only mode and no per-tool permission list. Every connection gets all 58 tools, and 35 of them write — 12 create, 13 update, 9 delete, and 1 replace, against 23 that only read. Connecting is not a read-only act: an assistant that can list your bookings can also cancel them.
Your API key is a password. Anyone holding it can read your bookings and contacts and make changes on your behalf. Never paste it into a public chat, a screenshot, a shared document, or a support ticket. If a key is exposed, rotate it immediately from Settings → Developer → API Keys.
Three habits keep this safe:
  • Use a dedicated key for MCP rather than reusing one that’s already wired into a production integration, so you can revoke it without breaking anything else.
  • Keep your client’s tool-approval prompts on while you get comfortable, so destructive actions like delete_eventtype or cancel_booking need a confirmation.
  • Hide the destructive tools if you connect through the mcp-remote bridge. It accepts --ignore-tool, which drops tools before your assistant ever sees them — the closest thing to a read-only mode:
    Add these to the args array alongside --header. See Connect your AI assistant. This filters at the bridge, not at Cal ID: the key itself still has full access, so it protects you from an assistant’s mistakes, not from a leaked key.
Cal ID checks your key only when a tool actually runs, not when a client connects. A wrong key still connects and still lists all 58 tools — see Verify the connection for the check that really tests it.

​
What MCP does not cover

The MCP server exposes the Cal ID REST API, so it inherits the same boundaries. These areas have no MCP tools and must be managed in the dashboard:
The tool list is generated from the API, so it grows as the API does. To see exactly what your connection offers today, ask your assistant to list its Cal ID tools, or run the tool check.

​
MCP or the REST API?

Both reach the same data. Choose by who is calling.
MCP cannot receive webhooks. It can create and manage webhook subscriptions, but the deliveries themselves go to your server. See Build a webhook receiver.

​
Start using the MCP server

Connect your AI assistant

Step-by-step setup for Claude, Cursor, ChatGPT, and other clients.

Tool reference

All 58 tools, grouped by what they do, plus the gotchas worth knowing.

Get your API key

Create, secure, and rotate the credential MCP authenticates with.

REST API reference

The full API behind every MCP tool.

Related topics

Connect Your AI Assistant to Cal IDCal ID MCP Tool ReferenceHow to Get Your Cal ID API KeyCal ID Scheduling API Reference