How to integrate Check Cherry MCP with Claude Agent SDK

This guide walks you through connecting Check Cherry to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Check Cherry agent that can list your appointments, check event availability, create appointments, track expenses, and view reports through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Check Cherry account through Composio's Check Cherry 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
Check Cherry logoCheck Cherry
Api Key

Check Cherry is a business management platform for photography and event service companies. It helps teams manage leads, bookings, appointments, offerings, payments, and workflows in one place.

25 Tools

Introduction

This guide walks you through connecting Check Cherry to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Check Cherry agent that can list your appointments, check event availability, create appointments, track expenses, and view reports through natural language commands.

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

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

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

The Check Cherry MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Check Cherry account. It provides structured and secure access to your leads, bookings, appointments, offerings, payments, expenses, questionnaires, and business reports, so your agent can manage schedules, review clients and events, track finances, update questionnaires, and check availability on your behalf.

  • Lead and booking management: Have your agent search leads, review proposals and confirmed bookings, and find package bookings by event date.
  • Appointments and availability: Let the agent check package availability, find open appointment times, schedule staff appointments for guests, and remove appointments from the active calendar.
  • Payments and expense tracking: Direct your agent to review event payments and refunds, record business expenses, update expense details, classify costs, or remove outdated expense records.
  • Questionnaire coordination: Instruct your agent to attach questionnaire templates to bookings, review questions and responses, update answers, and remove questionnaires when needed.
  • Offerings and business reporting: Have your agent review services, package groups, packages, and add-ons, then retrieve reports covering bookings, leads, payments, proposals, or projected revenue.

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

Attach Questionnaire

Copy a questionnaire template onto a proposal or confirmed booking.

Check Event Availability

Check whether a package can be booked on one date or across a date range.

Create Appointment

Create a staff appointment for a guest at a specific date, time, and duration; this changes the business calendar.

Create Expense

Record a business expense with its payment date, amount, reference, payee, and optional event and category links.

Delete Appointment

Soft-delete one appointment so it no longer appears in active business calendar records; Check Cherry retains the deleted record.

Delete Expense

Soft-delete one business expense so it no longer appears in listings; Check Cherry retains the record for record-keeping.

Get Appointment

Return full guest, scheduling, and assignment details for one appointment.

Get Event

Return full details for one proposal or confirmed booking by event ID.

Get Lead

Return full details for one lead by ID.

Get Questionnaire

Return one questionnaire with its questions, current answers, and completion state.

Get Report

Return one time-bucketed Check Cherry business report for bookings, leads, payments, proposals, or projected revenue.

List Appointments

Search staff appointments by date, assignee, brand, cancellation state, time direction, or text, returning one page.

List Appointment Slots

Return available appointment times for one staff member and appointment calendar on a selected date.

List Event Bookings

List package bookings attached to events within an optional event-date range, returning one page and a continuation cursor.

List Events

Search proposals and confirmed bookings with date, status, client, staff, payment, and workflow filters, returning one page.

List Expense Categories

Return the expense categories available for classifying business expenses.

List Expenses

Search business expenses by event, category, payment date, text, and sort order, returning one page.

List Leads

Search leads by exact email or contact and event text, returning one page of CRM records.

List Offerings

List one Check Cherry catalog resource: services, package groups, packages, or add-ons.

List Payments

List event payment records, including received payments and refunds, by event or payment date; returns one page with monetary values in Check Cherry's original representations.

List Questionnaires

List questionnaires attached to one event booking.

List Questionnaire Templates

Return questionnaire templates that can be attached to an event booking.

Remove Questionnaire

Detach one questionnaire from its event booking and delete its collected answers; the source questionnaire template is unchanged.

Update Expense

Change selected fields on an existing business expense.

Update Questionnaire Answers

Update answers on a standard questionnaire.

FRAMEWORKS

How to build Check Cherry MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Check Cherry MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Check Cherry MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Check Cherry MCP with Claude Cowork

Codex logo

Codex

Use Check Cherry MCP with Codex

OpenClaw logo

OpenClaw

Use Check Cherry MCP with OpenClaw

Hermes logo

Hermes

Use Check Cherry MCP with Hermes

CLI logo

CLI

Use Check Cherry MCP with CLI

Google ADK logo

Google ADK

Use Check Cherry MCP with Google ADK

LangChain logo

LangChain

Use Check Cherry MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Check Cherry MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Check Cherry MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Check Cherry MCP with LlamaIndex

CrewAI logo

CrewAI

Use Check Cherry MCP with CrewAI

FAQ

Frequently asked questions

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

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

Start with Check Cherry.It takes 30 seconds.

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