Provider REST API

18 actions

Connect Claude to Calendly

See event types, open times and scheduled meetings, and book, cancel or share single-use links in Calendly. Toolspoke puts 18 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: 18
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Calendly
Open the marketplace in your workspace, add Calendly 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. Calendly 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 Calendly 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.

Personal access tokenRequired: Calendly → Integrations & apps → API and webhooks → Personal access tokens → Get a token. The token acts as you; organization-wide lists need an admin's token.

What Claude can do in Calendly

18 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: 14Reads
Writes: 2Writes
Destructive: 2Destructive

Reads

Fetches data and changes nothing.

get_current_user
Read the user the token belongs to. Returns resource.uri (the user URI) and current_organization (the organization URI) - the two values almost every other call here needs. Call this first.
list_event_types
List event types - the bookable meeting kinds - for a user or a whole organization. Give user or organization.
get_event_type
Read one event type - name, length, scheduling URL, locations and the custom questions invitees answer.
list_event_type_available_times
List the open start times for one event type in a window of up to 7 days. Times are UTC.
list_user_busy_times
List a user's busy blocks - Calendly meetings and connected-calendar events - in a window of up to 7 days. Times only, no event titles from external calendars.
list_user_availability_schedules
List a user's availability schedules - weekly hours, date overrides and time zone.
list_scheduled_events
List scheduled meetings for a user or organization, filtered by time window, status or invitee email. Give user or organization.
get_scheduled_event
Read one scheduled meeting - times, event type, location, hosts and invitee counts.
list_event_invitees
List the invitees of one scheduled meeting, with their email, time zone and their answers to the booking questions.
get_event_invitee
Read one invitee of a scheduled meeting - contact details, answers, reschedule and cancel links, and no-show status.
list_organization_memberships
List the members of an organization with their role, or find one by email. Give organization or user.
list_routing_forms
List an organization's routing forms - the qualifying questionnaires that send a visitor to the right event type.
list_routing_form_submissions
List the answers people submitted to one routing form, and where each was routed.
list_webhook_subscriptions
List webhook subscriptions for an organization, or for one user in it.

Writes

Creates or updates something on the other side.

create_scheduling_link
Create a single-use booking link for one event type. Nothing is sent to anyone - the link is returned for you to share, and it stops working after one booking.
mark_invitee_no_show
Mark an invitee as a no-show. Nobody is notified, and it can be removed again in Calendly.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

book_meeting
Book a meeting directly, as the invitee would. Destructive rather than write: Calendly emails the invitee and hosts and puts it in their calendars immediately. start_time must be one of the times list_event_type_available_times returned.
cancel_scheduled_event
Cancel a scheduled meeting. Every invitee is emailed the cancellation at once, and it cannot be undone.

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 18 actions above are the whole of it. A call to any other name is refused before it reaches Calendly 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 Calendly 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 Calendly: 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 Calendly. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Calendly's own rate limits. A call that Calendly refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Calendly?

18 named actions: 14 that only read, 2 that write and 2 that delete or permanently alter something. They include get_current_user, 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 Calendly connector need?

API key. The connector asks for personal access token. 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 Calendly connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 18 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 Calendly connector not do?

The 18 actions above are the whole of it. A call to any other name is refused before it reaches Calendly 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 Calendly 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 Calendly. An agent has to ask. Toolspoke does not retry, queue or back off around Calendly's own rate limits. A call that Calendly 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 Calendly'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 Calendly?

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