# Your booked calls. Ready before they start.

Source: https://corespeed.io/integrations/calendly

Connect Calendly to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads your event types, a page of up to 100 scheduled events and their invitees, and lists who booked each call and when. It signs in with your own Calendly account, and cancelling an event is a separate call that approvals can hold.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Calendly after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Know who is booked. Start the day prepared

Ask your agent for the Calendly events it can see and their invitees, gathered into one list before the first call.

You ask your agent: "List the active Calendly events you can see, with each invitee and the meeting type. Put tomorrow's in order and note any back-to-back calls. Do not cancel anything."

It calls CoreSpeed:

- `calendly__list_scheduled_events`: ok, 392 ms
- `calendly__list_event_invitees`: ok, 318 ms

It reads from: Calendly.

### Tomorrow's calls: Three calls, in order.

Of the events Calendly returned, three are tomorrow. The demo ends at 11:45, with time to prepare before 15:00.

**Calls**

- 9:30 Intro call with Stewart.
- 11:00 Product demo with Jessica.
- 15:00 Intro call with Parker.

_Illustrative example · Fictional data · No event cancelled_

All connectors: https://corespeed.io/docs/connectors

## From bookings to a prepared day

Requests you can make once Calendly is connected. The data is fictional.

### See tomorrow's calls

Tomorrow · scheduled events · Scheduled events

- Booked: 3 calls
- First: Intro call, 9:30
- From the events Calendly returns

### Know who is coming

Product demo · invitees · Invitees

- Invitee: Jessica
- Booked: Monday, through your demo link
- Read only

### Cancel with a check

A double booking · Approvals

- Event: Intro call, Parker, 15:00
- Rule: Ask before cancelling an event
- Waiting for you

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Calendly**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Can the agent book a new meeting in Calendly?

No. The Calendly tools read your event types, events and invitees, and cancel an event. Invitees still book through your scheduling link.

### Can the agent cancel a meeting on its own?

Cancelling is a separate tool call that notifies the invitee. Approvals can hold it until a person agrees. How approvals work: https://corespeed.io/docs/approvals

### Does the agent see every Calendly event?

Not always. Each call returns up to 100 events with no date filter, so the list for a busy account can stop short.

### Whose events can the agent see?

The events of the Calendly account that connected. Access follows that account and its permissions.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/calendly

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [Ashby for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/ashby): Bring your Ashby jobs, candidates and interviews into your agent. Get a pipeline summary without changing a stage.
- [Cal.com for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/cal): See your Cal.com bookings and availability inside your agent. Booking or cancelling a slot stays a separate, visible step.
- [Fathom for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/fathom): Bring Fathom meeting summaries, transcripts and action items into your agent. Draft the follow-up without replaying the call.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Calendly API reference: https://developer.calendly.com/api-docs

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)