How to integrate Calendly MCP with CrewAI

This guide walks you through connecting Calendly to CrewAI 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 CrewAI 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.

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 CrewAI 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 CrewAI 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

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Calendly connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Calendly
  • Build a conversational loop where your agent can execute Calendly operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Calendly connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Calendly via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Calendly MCP URL
6

Create a Composio Tool Router session for Calendly

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["calendly"])

url = session.mcp.url
What's happening:
  • You create a Calendly only session through Composio
  • Composio returns an MCP HTTP URL that exposes Calendly tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Calendly and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["calendly"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Calendly through Composio's Tool Router. The agent can perform Calendly operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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.

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. CrewAI 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