How to integrate Check Cherry MCP with Mastra AI

This guide walks you through connecting Check Cherry to Mastra AI 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 Mastra AI 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 Mastra AI 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 Mastra AI 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 Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKLlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Check Cherry tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Check Cherry tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Check Cherry agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Check Cherry through MCP.
3

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models
5

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session
6

Create a Tool Router session for Check Cherry

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["check_cherry"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Check Cherry MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "check_cherry" for Check Cherry access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
7

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Check Cherry toolkit
8

Create the Mastra agent

typescript
const agent = new Agent({
    name: "check_cherry-mastra-agent",
    instructions: "You are an AI agent with Check Cherry tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM
9

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        check_cherry: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Check Cherry toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Check Cherry and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["check_cherry"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      check_cherry: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "check_cherry-mastra-agent",
    instructions: "You are an AI agent with Check Cherry tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { check_cherry: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Check Cherry through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows
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 Agent SDK logo

Claude Agent SDK

Use Check Cherry MCP with Claude Agent 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

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. Mastra AI 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