Calendly with Claude Agent SDK

How to integrate Calendly MCP with Claude Agent SDK

Q: What are the differences in Tool Router MCP and Calendly MCP?

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.

Q: Can I use Tool Router MCP with Claude Agent SDK?

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.

Q: Can I manage the permissions and scopes for Calendly while using Tool Router?

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.

Q: How safe is my data with Composio Tool Router?

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.

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Calendly with TL;DR What is Claude Agent SDK What is the Calendly MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Calendly MCP Agent with another framework Explore Other Toolkits FAQ

Connect Calendly without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

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

ChatGPT OpenAI Agents SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

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.

Supported Tools & Triggers

Tools

Cancel scheduled eventTool to cancel a scheduled Calendly event by creating a cancellation record.

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

Create One-Off Event TypeCreates 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 linkCreate a single-use scheduling link.

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

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

Create webhook subscriptionTool to create a webhook subscription for receiving Calendly event notifications.

Delete invitee dataPermanently 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 showDeletes 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 membershipTool to remove a user from a Calendly organization by membership UUID.

Delete scheduled event dataFor 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 subscriptionDeletes an existing webhook subscription to stop Calendly sending event notifications to its registered callback URL; this operation is idempotent.

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

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

Get event typeRetrieves 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 availabilityTool to retrieve availability schedules configured for a specific Calendly event type.

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

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

Get invitee no showRetrieves 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 organizationTool to retrieve information about a specific Calendly organization.

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

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

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

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

Get sample webhook dataTool to retrieve sample webhook payload data for testing webhook subscriptions.

Get userRetrieves comprehensive details for an existing Calendly user.

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

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

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

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

List event inviteesRetrieves 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 timesFetches available time slots for a Calendly event type within a specified time range; results are not paginated.

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

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

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

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

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

List organization membershipsRetrieves a list of organization memberships.

List outgoing communicationsRetrieves 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 formsRetrieves routing forms for a specified organization; routing forms are questionnaires used to direct invitees to appropriate booking pages or external URLs.

List scheduled eventsTool to retrieve a list of scheduled Calendly events.

List user availability schedulesRetrieves all availability schedules for the specified Calendly user.

List user busy timesFetches 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 LocationsTool to retrieve configured meeting location information for a given Calendly user.

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

Invite user to organizationTool to invite a user to a Calendly organization via email.

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

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

Revoke a user's organization invitationRevokes 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 TypeTool to update an existing one-on-one event type (kind: solo) in Calendly.

Update Event Type AvailabilityTool to update an event type availability schedule in Calendly.

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:

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

Step-by-step Guide

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

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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

composio-anthropic provides Composio integration for Anthropic
claude-agent-sdk is the core agent framework
python-dotenv loads environment variables

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

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The load_dotenv() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Calendly functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Calendly
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["calendly"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

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

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Calendly tools via Composio.",
    max_turns=10
)

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permission_mode="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
max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()

What's happening:

The Claude SDK client is created using the async context manager pattern
The agent processes each query and streams the response back in real-time
The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

What's happening:

This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Calendly
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["calendly"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Calendly tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

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.

How to build Calendly MCP Agent with another framework

ChatGPT

Use Calendly MCP with ChatGPT

OpenAI Agents SDK

Use Calendly MCP with OpenAI Agents SDK

Claude Code

Use Calendly MCP with Claude Code

Claude Cowork

Use Calendly MCP with Claude Cowork

Codex

Use Calendly MCP with Codex

Cursor

Use Calendly MCP with Cursor

OpenClaw

Use Calendly MCP with OpenClaw

Hermes

Use Calendly MCP with Hermes

CLI

Use Calendly MCP with CLI

Google ADK

Use Calendly MCP with Google ADK

LangChain

Use Calendly MCP with LangChain

Vercel AI SDK

Use Calendly MCP with Vercel AI SDK

Mastra AI

Use Calendly MCP with Mastra AI

LlamaIndex

Use Calendly MCP with LlamaIndex

CrewAI

Use Calendly MCP with CrewAI

OpenCode

Use Calendly MCP with OpenCode

VS Code

Use Calendly MCP with VS Code

Explore Other Toolkits

Google Calendar

Oauth2

Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.

Apaleo

Oauth2

Apaleo is a cloud-based property management platform for hospitality businesses. It centralizes reservations, billing, and daily operations for smoother hotel management.

Appointo

Api Key

Appointo is an appointment booking platform for Shopify stores. It lets businesses add online scheduling to their websites with zero coding.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Calendly MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

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.

Can I manage the permissions and scopes for Calendly while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

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

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

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

Ryan YuFounder, Extra Thursday

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

Tomisin JenrolaFounder & CEO, SwarmZero

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

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Calendly MCP with Claude Agent SDK

Table of Contents

Connect Calendly without Auth hassles

Introduction

Also integrate Calendly with

TL;DR

What is Claude Agent SDK?

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

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

How to build Calendly MCP Agent with another framework

ChatGPT

OpenAI Agents SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

OpenCode

VS Code

Explore Other Toolkits

Google Calendar

Apaleo

Appointo

FAQ

What are the differences in Tool Router MCP and Calendly MCP?

Can I use Tool Router MCP with Claude Agent SDK?

Can I manage the permissions and scopes for Calendly while using Tool Router?

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability