How to integrate Calendly MCP with Claude Agent SDK

This guide walks you through connecting Calendly to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Calendly agent that can create a single-use scheduling link for your next meeting, cancel your 2pm event with a reason, mark an invitee as no-show for today's appointment through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Calendly account through Composio's Calendly MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Calendly logoCalendly
Oauth2

Calendly is an appointment scheduling tool that automates meeting invitations, availability checks, and reminders. It helps individuals and teams avoid endless email back-and-forth when booking meetings.

51 Tools

Introduction

This guide walks you through connecting Calendly to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Calendly agent that can create a single-use scheduling link for your next meeting, cancel your 2pm event with a reason, mark an invitee as no-show for today's appointment through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Calendly account through Composio's Calendly MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Calendly with

ChatGPTOpenAI Agents SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Calendly
  • Configure an AI agent that can use Calendly as a tool
  • Run a live chat session where you can ask the agent to perform Calendly operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Calendly MCP server, and what's possible with it?

The Calendly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Calendly account. It provides structured and secure access to your scheduling workflows, so your agent can perform actions like creating personalized scheduling links, managing events, handling invitee statuses, and automating reminders on your behalf.

  • Instant scheduling link creation: Direct your agent to generate single-use or shareable scheduling links so others can book time with you instantly—no more back-and-forth emails.
  • Automated event and invitee management: Have your agent cancel events, mark invitees as no-shows, or remove no-show statuses to keep your calendar accurate and up to date.
  • Custom one-off event setup: Empower your agent to create unique, one-off meeting types for special situations, bypassing your regular availability rules.
  • Webhook subscription automation: Let the agent set up webhook subscriptions to trigger notifications or workflows in real time when events happen in your Calendly account.
  • Data privacy and compliance actions: Instruct your agent to delete invitee data or scheduled event records as needed for privacy or regulatory compliance, especially for enterprise use cases.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Calendly account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Calendly functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Calendly
  const session = await composio.create(USER_ID, {
    toolkits: ['calendly'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Calendly
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Calendly tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Calendly
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Calendly and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['calendly']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Calendly tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Calendly through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Calendly action and event your agent gets out of the box.

Cancel scheduled event

Tool to cancel a scheduled Calendly event by creating a cancellation record.

Create Event Type

Tool to create a new one-on-one event type (kind: solo) in Calendly.

Create One-Off Event Type

Creates a temporary Calendly one-off event type for unique meetings outside regular availability, requiring valid host/co-host URIs, a future date/range for `date_setting`, and a positive `duration`.

Create scheduling link

Create a single-use scheduling link.

Create share

Creates a customizable, one-time share link for a Calendly event type, allowing specific overrides to its settings (e.

Create single use scheduling link

Creates a one-time, single-use scheduling link for an active Calendly event type, expiring after one booking.

Create webhook subscription

Tool to create a webhook subscription for receiving Calendly event notifications.

Delete invitee data

Permanently removes all invitee data associated with the provided emails from past organization events, for data privacy compliance (requires Enterprise subscription; deletion may take up to one week).

Delete invitee no show

Deletes an Invitee No-Show record by its `uuid` to reverse an invitee's 'no-show' status; the `uuid` must refer to an existing record.

Delete organization membership

Tool to remove a user from a Calendly organization by membership UUID.

Delete scheduled event data

For Enterprise users, initiates deletion of an organization's scheduled event data between a `start_time` and `end_time` (inclusive, where `start_time` must be <= `end_time`); actual data deletion may take up to 7 days to complete.

Delete webhook subscription

Deletes an existing webhook subscription to stop Calendly sending event notifications to its registered callback URL; this operation is idempotent.

Get event

Use to retrieve a specific Calendly scheduled event by its UUID, provided the event exists in the user's Calendly account.

Get event invitee

Retrieves detailed information about a specific invitee of a scheduled event, using their unique UUIDs.

Get event type

Retrieves details for a specific Calendly event type, identified by its UUID, which must be valid and correspond to an existing event type.

Get event type availability

Tool to retrieve availability schedules configured for a specific Calendly event type.

Get group

Retrieves all attributes of a specific Calendly group by its UUID; the group must exist.

Get group relationship

Retrieves a specific Calendly group relationship by its valid and existing UUID, providing details on user-group associations and membership.

Get invitee no show

Retrieves details for a specific Invitee No Show record by its UUID; an Invitee No Show is marked when an invitee does not attend a scheduled event.

Get organization

Tool to retrieve information about a specific Calendly organization.

Get organization invitation

Retrieves a specific Calendly organization invitation using its UUID and the parent organization's UUID.

Get organization membership

Retrieves a specific Calendly organization membership by its UUID, returning all its attributes.

Get routing form

Retrieves a specific routing form by its UUID, providing its configuration details including questions and routing logic.

Get routing form submission

Tool to retrieve details about a specific routing form submission by its UUID.

Get sample webhook data

Tool to retrieve sample webhook payload data for testing webhook subscriptions.

Get user

Retrieves comprehensive details for an existing Calendly user.

Get user availability schedule

Retrieves an existing user availability schedule by its UUID; this schedule defines the user's default hours of availability.

Get webhook subscription

Retrieves the details of an existing webhook subscription, identified by its UUID, including its callback URL, subscribed events, scope, and state.

Mark invitee as no-show

Tool to mark an invitee as a no-show for a scheduled event.

List activity log entries

Retrieves a list of activity log entries for a specified Calendly organization (requires an active Enterprise subscription), supporting filtering, sorting, and pagination.

List event invitees

Retrieves a list of invitees for a specified Calendly event UUID, with options to filter by status or email, and sort by creation time.

List event type available times

Fetches available time slots for a Calendly event type within a specified time range; results are not paginated.

List event type hosts

Tool to retrieve a list of event type hosts (memberships) for a specific event type.

List Event Types

Tool to list all Event Types associated with a specified User or Organization.

List group relationships

Retrieves a list of group relationships defining an owner's role (e.

List groups

Returns a list of groups for a specified Calendly organization URI, supporting pagination.

List organization invitations

Retrieves a list of invitations for a specific organization, identified by its UUID.

List organization memberships

Retrieves a list of organization memberships.

List outgoing communications

Retrieves a list of outgoing SMS communications for a specified organization; requires an Enterprise subscription and if filtering by creation date, both `min_created_at` and `max_created_at` must be provided to form a valid range.

List routing forms

Retrieves routing forms for a specified organization; routing forms are questionnaires used to direct invitees to appropriate booking pages or external URLs.

List scheduled events

Tool to retrieve a list of scheduled Calendly events.

List user availability schedules

Retrieves all availability schedules for the specified Calendly user.

List user busy times

Fetches a user's busy time intervals (internal and external calendar events) in ascending order for a period up to 7 days; keyset pagination is not supported.

List User Meeting Locations

Tool to retrieve configured meeting location information for a given Calendly user.

List webhook subscriptions

Retrieves webhook subscriptions for a Calendly organization; `scope` determines if `user` or `group` URI is also required for filtering.

Invite user to organization

Tool to invite a user to a Calendly organization via email.

Create Event Invitee

Tool to create a new Event Invitee with standard notifications, calendar invites, reschedules, and workflows.

Remove user from organization

Removes a user (who is not an owner) from an organization by their membership UUID, requiring administrative privileges.

Revoke a user's organization invitation

Revokes a pending and revokable (not yet accepted or expired) organization invitation using its UUID and the organization's UUID, rendering the invitation link invalid.

Update Event Type

Tool to update an existing one-on-one event type (kind: solo) in Calendly.

Update Event Type Availability

Tool to update an event type availability schedule in Calendly.

FRAMEWORKS

How to build Calendly MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Calendly MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Calendly MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Calendly MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Calendly MCP with Claude Cowork

Codex logo

Codex

Use Calendly MCP with Codex

Cursor logo

Cursor

Use Calendly MCP with Cursor

OpenClaw logo

OpenClaw

Use Calendly MCP with OpenClaw

Hermes logo

Hermes

Use Calendly MCP with Hermes

CLI logo

CLI

Use Calendly MCP with CLI

Google ADK logo

Google ADK

Use Calendly MCP with Google ADK

LangChain logo

LangChain

Use Calendly MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Calendly MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Calendly MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Calendly MCP with LlamaIndex

CrewAI logo

CrewAI

Use Calendly MCP with CrewAI

OpenCode logo

OpenCode

Use Calendly MCP with OpenCode

VS Code logo

VS Code

Use Calendly MCP with VS Code

FAQ

Frequently asked questions

With a standalone Calendly MCP server, the agents and LLMs can only access a fixed set of Calendly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Calendly and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Calendly tools.

Yes, absolutely. You can configure which Calendly scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Calendly data and credentials are handled as safely as possible.

Start with Calendly.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Calendly tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies