Calendly MCP review and Yalc Framework

Install

Add Calendly to Claude Code in one command

claude mcp add calendly-composio --transport http "YOUR_COMPOSIO_MCP_URL" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

Calendly is distributed through Composio rather than as a standalone MCP. Generate the MCP URL with the Composio Python SDK using `composio.create(user_id, toolkits=["calendly"])`. Get a Composio API key from composio.dev. Replace both placeholders, run the command, restart Claude Code, then complete OAuth on first call.

What it does

Calendly, plainly

Calendly's MCP exposes scheduled events, invitees, event types, organization data, and user data as native Claude tool calls. Auth runs through Composio's OAuth proxy, which means one Composio API key plus an OAuth dance gives Yalc access to your Calendly account.

For Yalc operators, Calendly is the inbound side of the scheduling surface. Where Google Calendar handles outbound holds and team coordination, Calendly handles "people booking time with you". The MCP lets Yalc workflows answer "who booked a call this week", "what's the booking conversion rate by source", and "which event types are converting".

Where it slots in

Position in the GTM operating system

Intake

→

Enrich

→

Score

→

Route

→

Draft

→

Send

→

Listen

The Calendly MCP sits at the **route** node when inbound bookings need to flow into Yalc workflows. It pairs with Gmail (warm thread context), Google Calendar (the actual event), Notion or HubSpot (CRM writeback), and Slack (team notification).

Most useful patterns: morning briefings ("who booked discovery this week and what should I prep"), pipeline analysis ("conversion rate from booking to closed"), and event type optimization ("which event types are converting and which are noise").

The Yalc Framework

Deploying the Calendly MCP inside Yalc workflows

Workflow position

The inbound booking node. Yalc reads booking events, joins with CRM context, and triggers downstream actions (prep notes, AM assignment, confirmation emails).

Prompt patterns

Copy paste prompts for Claude Code that invoke the Calendly MCP.

Yalc, every Monday at 8am pull this week's Calendly bookings. For each one, look up the booker in HubSpot, generate a prep note from prior touchpoints, and write to a "Discovery prep" Notion page. → Yalc reads Calendly events via MCP, joins with HubSpot, writes to Notion.

Yalc, count last month's Calendly bookings grouped by source (UTM source from the booking URL). Surface the top 3 performing sources for the next campaign cycle. → Yalc reads the booking data, classifies by UTM, returns a source breakdown.

Yalc, when a new Calendly booking comes in for the "Discovery" event type, alert me on Slack with the booker's company and recent LinkedIn posts. → Yalc subscribes via webhook, enriches via Crustdata MCP, posts via Slack MCP.

Chaining recommendations

UpstreamBooker selects time on Calendly → Calendly webhook → Yalc workflow trigger

DownstreamCalendly event → Gmail (confirmation) or Notion (prep) or Slack (alert)

Anti patterns to avoid

Don't read every booking event on every workflow run. Cache or use webhooks for real time. Polling Calendly burns API quota fast.

Don't try to create Calendly events programmatically. Calendly is for invitee bookings; create events via Google Calendar MCP instead.

Don't dual sync Calendly bookings to multiple CRMs. Pick one as the destination (HubSpot or Notion) to avoid double counting.

Compatibility

Distributed via Composio's MCP gateway. Works in Claude Code, Cursor, Codex, Claude Desktop. Calendly's API has standard rate limits per OAuth token. For agency setups with multiple Calendly accounts, register the MCP multiple times with different Composio sessions.

Operator take

Pros, cons, who it's for

Pros

One MCP covers the read side of the full Calendly surface (events, invitees, event types)
OAuth proxy through Composio handles auth complexity
Webhook support for real time booking events
Pairs cleanly with Google Calendar MCP for full scheduling coverage
Free tier of Composio sufficient for single Calendly account piloting

Cons

Requires Composio account and API key (extra vendor in the chain)
Rate limits surface fast on heavy polling; webhooks recommended for production
No event creation via the MCP; Calendly is invitee-driven by design
Multi account setups require multiple Composio sessions

Who it's for

Founders and AMs who run discovery calls through Calendly
GTM teams that want booking data inside Claude Code workflows
Operators building "automatic discovery prep" workflows

Google Calendar MCP

Pair both. Google Calendar for outbound scheduling, Calendly for inbound bookings.

→

Alternatives

MCPs to consider instead

Cal.com MCP

Switch when your team is on Cal.com instead of Calendly.

→

Direct Calendly webhook handler

Skip the MCP for high volume real time event handling. Direct webhooks are more efficient.

→

Google Calendar MCP only

Skip Calendly entirely if you don't run inbound booking. Google Calendar covers outbound coordination.

→

FAQ

Frequently asked

Why is Calendly distributed via Composio instead of a direct MCP?

Composio operates the MCP infrastructure for many SaaS vendors including Calendly. You get OAuth, refresh token handling, and tool exposure managed by Composio. The trade off is one extra vendor in the chain.

Do I need a Composio account for Calendly?

Yes. The Composio API key is required to generate the MCP URL. Composio has a free tier sufficient for piloting a single Calendly account.

Can the MCP create Calendly bookings?

No. Calendly is invitee-driven by design. The MCP reads booking data; for creating events programmatically, use the Google Calendar MCP.

How does Calendly compare to Cal.com?

Calendly is more mature with broader integrations. Cal.com is open source with stronger team scheduling features. Pick based on which one your team uses; the MCPs cover similar surfaces.

How do I handle real time booking events?

Calendly's webhook API is first class. Set up a webhook endpoint that posts to your Yalc workflow on each new booking. The MCP itself is for reads; webhooks for real time triggers.

Will the MCP burn through Calendly API limits?

For typical Yalc volume (a few hundred booking reads per day), no. For high frequency polling, switch to webhooks. Calendly's rate limits are stricter than HubSpot or Notion.

Calendly MCP and the Yalc Framework