How to integrate Calendarhero MCP with Claude Agent SDK

GET STARTED FOR FREE
Calendarhero logo
Claude Agent SDK logo
divider

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

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.

Supported Tools & Triggers

Tools
Add Calendar ConnectionTool to add a calendar integration to a user's account.
Create ContactTool to create a new contact.
Create Meeting Request V2Tool to create a new meeting request in calendarhero.
Fetch ContactFetch contact
Fetch Meeting DetailsTool to fetch details for meetings within a specified timeframe.
Fetch User ProfileTool to fetch the profile details of the authenticated user.
List MeetingsTool to retrieve the user's meetings within a specified timeframe.
List Meeting TemplatesTool to list all meeting templates available for quick scheduling.
List Meeting TypesTool to retrieve the user's configured meeting types.
List User CalendarsTool to list all calendar integrations connected to a user's calendarhero account.
Search ContactTool to search for existing contacts.
Send ReminderTool to send a reminder to a contact about their scheduled meeting.
Update ContactTool to update details of an existing contact.

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

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

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 Calendarhero 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 Calendarhero
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["calendarhero"]
    )

    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 Calendarhero
  • 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 Calendarhero 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 Calendarhero
  • 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 Calendarhero 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 Calendarhero
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["calendarhero"]
    )

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

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

Codex logo

Codex

Use Calendarhero MCP with Codex

OpenClaw logo

OpenClaw

Use Calendarhero MCP with OpenClaw

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

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

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.

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 Calendarhero tools.

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

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.

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 Calendarhero data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

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

Book a call↗Get started for free