Provider REST API

16 actions

Connect Claude to Cal.com

Find open slots, and book, reschedule or cancel meetings on Cal.com, cloud or self-hosted. Toolspoke puts 16 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 16
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Cal.com
Open the marketplace in your workspace, add Cal.com to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Cal.com shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Cal.com asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired: Cal.com → Settings → Developer → API Keys → Add. The key acts as the user who created it.; cal_live_…
API URLOptional: Leave blank for cal.com. For a self-hosted Cal.com, the origin your API v2 server is served from, with no trailing path - this connector adds /v2 itself. It has to be reachable from this gateway.; https://api.cal.com

What Claude can do in Cal.com

16 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 10Reads
Writes: 1Writes
Destructive: 5Destructive

Reads

Fetches data and changes nothing.

get_me
Read the profile of the user the API key belongs to - username, email, time zone, week start and default schedule.
list_event_types
List event types - the bookable meeting kinds with their slug, length and locations. With no arguments, the key owner's own; with username, someone else's public ones.
get_event_type
Read one event type in full - length, locations, booking fields, limits and the schedule it books against.
get_available_slots
List open slots for an event type between two times. Identify the event type by eventTypeId, or by eventTypeSlug plus username. Times are UTC ISO 8601; timeZone sets the zone the slots come back in.
list_bookings
List bookings with their attendees, times, status and location. Filter by status, attendee, event type or time window.
get_booking
Read one booking - attendees, times, status, location, the answers the attendee gave and any cancellation reason.
list_schedules
List the key owner's availability schedules - working hours per weekday, date overrides and time zone.
get_default_schedule
Read the key owner's default availability schedule.
list_calendars
List the calendars connected to Cal.com, with the credentialId and externalId get_busy_times needs.
get_busy_times
Read the busy blocks on one connected calendar between two dates. Times only, no event titles.

Writes

Creates or updates something on the other side.

mark_booking_absent
Record a no-show on a past booking - the host, some attendees, or both. Nobody is notified and it can be set back.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

create_booking
Book a meeting for an attendee. Destructive rather than write: Cal.com emails the attendee a confirmation and puts the meeting in their calendar the moment it succeeds. Check get_available_slots first; start must be one of the open slots.
reschedule_booking
Move a booking to a new start time. Destructive because Cal.com emails every attendee the change at once.
cancel_booking
Cancel a booking. Attendees are emailed at once and the slot is released; there is no undo.
confirm_booking
Accept a booking that is waiting for confirmation. Destructive because the attendee is emailed the confirmation at once.
decline_booking
Decline a booking that is waiting for confirmation. The attendee is emailed at once.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 16 actions above are the whole of it. A call to any other name is refused before it reaches Cal.com rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Cal.com of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Cal.com: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Cal.com. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Cal.com's own rate limits. A call that Cal.com refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Cal.com?

16 named actions: 10 that only read, 1 that write and 5 that delete or permanently alter something. They include get_me, list_event_types and get_event_type. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Cal.com connector need?

API key. The connector asks for api key, and optionally api url. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Cal.com connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 16 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Cal.com connector not do?

The 16 actions above are the whole of it. A call to any other name is refused before it reaches Cal.com rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Cal.com of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Cal.com. An agent has to ask. Toolspoke does not retry, queue or back off around Cal.com's own rate limits. A call that Cal.com refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Cal.com's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Cal.com?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More productivity connectors

Browse all of them