How to integrate Calendarhero MCP with Claude Agent SDK

This guide walks you through connecting Calendarhero to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Calendarhero agent that can schedule a meeting with your project team, list all meetings i have this week, fetch details for your next scheduled meeting through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Calendarhero account through Composio's Calendarhero 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
Calendarhero logoCalendarhero
Api Key

Calendarhero is a powerful scheduling platform that streamlines your calendar management across multiple services. It helps you efficiently schedule, reschedule, and organize meetings without the back-and-forth.

38 Tools

Introduction

This guide walks you through connecting Calendarhero to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Calendarhero agent that can schedule a meeting with your project team, list all meetings i have this week, fetch details for your next scheduled meeting through natural language commands.

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

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

Also integrate Calendarhero with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle 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 Calendarhero
  • Configure an AI agent that can use Calendarhero as a tool
  • Run a live chat session where you can ask the agent to perform Calendarhero 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 Calendarhero MCP server, and what's possible with it?

The Calendarhero MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Calendarhero account. It provides structured and secure access to your calendar management tools, so your agent can schedule meetings, manage contacts, fetch meeting details, and access your calendar integrations on your behalf.

  • Automated meeting scheduling and requests: Easily have your agent schedule new meetings, select participants, set time ranges, and include extra meeting details in just a few steps.
  • Contact creation and management: Let the agent create new contacts or fetch existing ones, so scheduling is always quick and accurate.
  • Meeting details retrieval: Ask your agent to fetch specific meeting details or get a list of all meetings within a defined timeframe, keeping you up-to-date.
  • Access and manage calendar integrations: Direct your agent to list all connected calendars, add new integrations, or access available calendars for streamlined scheduling.
  • Template and meeting type discovery: Quickly retrieve available meeting templates and types, letting your agent optimize scheduling based on your preferences and routines.

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 Calendarhero 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 Calendarhero 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 Calendarhero
  const session = await composio.create(USER_ID, {
    toolkits: ['calendarhero'],
  });
  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 Calendarhero
  • 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 Calendarhero 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 Calendarhero
  • 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 Calendarhero 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: ['calendarhero']
  });
  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 Calendarhero 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 Calendarhero 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 Calendarhero action and event your agent gets out of the box.

Add Calendar Connection

Add a new calendar directory/connection to the user's CalendarHero account.

Create Contact

Creates a new contact in CalendarHero with the provided contact information.

Create Meeting Request V2

Tool to create a new meeting request in CalendarHero.

Create Webhook

Creates or updates a webhook for a specific event type in CalendarHero.

Delete Contact

Tool to delete a contact from CalendarHero by its unique identifier.

Delete Meeting Task

Tool to delete a meeting task/request from CalendarHero.

Delete Meeting Type

Tool to delete a meeting type from the authenticated user's CalendarHero account.

Delete User Directory

Tool to delete a user directory by its UUID.

Delete Webhook

Tool to delete a webhook subscription for a specific event type.

Fetch Contact

Fetch Contact

Fetch Meeting Details

Tool to fetch details for meetings within a specified timeframe.

Fetch User Profile

Tool to fetch the profile details of the authenticated user.

Get Assistant Message

Tool to retrieve a reply message from the CalendarHero assistant.

Get Contact Count

Tool to get the total count of contacts in CalendarHero.

Get Meeting Categories

Retrieves the user's meeting categories' stats for a specified time period.

Get Meeting Tasks

Retrieves the user's meeting requests/tasks from CalendarHero.

Get Search Result

Tool to get a search result by ID.

Get User Directory

Tool to retrieve a user's directory by its unique identifier.

Get User Organization

Tool to retrieve the authenticated user's organization details.

Get User Savings

Tool to retrieve the authenticated user's savings information from CalendarHero.

Get Webhook Configuration

Tool to get webhook configuration for a specific event type.

Get Webhook Sample

Tool to retrieve a sample webhook payload for a specific event type.

List Meeting Templates

Retrieves all meeting templates (reusable meeting configurations) for the authenticated user.

List Meeting Types

Retrieves all meeting types configured for the authenticated CalendarHero user.

List User Calendars

Tool to list all calendar integrations connected to a user's CalendarHero account.

List User Directories

Tool to retrieve all directories configured for a user.

Search Contact

Tool to search for existing contacts.

Search Integrations

Tool to search across all user integrations for a query term.

Send Assistant Message

Tool to send a user's message into the CalendarHero assistant.

Send Reminder

Sends an email reminder to all contacts/participants about a scheduled meeting request.

Update Contact

Updates an existing contact in CalendarHero with new information.

Update Meeting Types

Tool to update meeting type configurations for the authenticated CalendarHero user.

Update Restricted Apps

Tool to update the authenticated user's restricted apps settings.

Update User

Tool to update the authenticated user's profile information.

Update User Address

Tool to update the authenticated user's address settings by providing latitude and longitude coordinates.

Update User Directory

Tool to update a user's directory in CalendarHero.

Update User Info

Updates the authenticated user's info settings in CalendarHero.

Update Work Location

Tool to update the user's work location settings in CalendarHero.

FRAMEWORKS

How to build Calendarhero MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Calendarhero MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Calendarhero MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Calendarhero MCP with Claude Cowork

Codex logo

Codex

Use Calendarhero MCP with Codex

OpenClaw logo

OpenClaw

Use Calendarhero MCP with OpenClaw

Hermes logo

Hermes

Use Calendarhero MCP with Hermes

CLI logo

CLI

Use Calendarhero MCP with CLI

Google ADK logo

Google ADK

Use Calendarhero MCP with Google ADK

LangChain logo

LangChain

Use Calendarhero MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Calendarhero MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Calendarhero MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Calendarhero MCP with LlamaIndex

CrewAI logo

CrewAI

Use Calendarhero MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Calendarhero MCP server, the agents and LLMs can only access a fixed set of Calendarhero tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Calendarhero 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 Calendarhero tools.

Yes, absolutely. You can configure which Calendarhero 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 Calendarhero data and credentials are handled as safely as possible.

Start with Calendarhero.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Calendarhero 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