How to integrate Check Cherry MCP with Google ADK

This guide walks you through connecting Check Cherry to Google ADK 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 Google ADK 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.

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 Google ADK 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 Google ADK 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

TL;DR

Here's what you'll learn:
  • Get a Check Cherry account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Check Cherry
  • Build an agent that connects to Check Cherry through MCP
  • Interact with Check Cherry using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Check Cherry via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["check_cherry"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Check Cherry operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Check Cherry and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["check_cherry"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Check Cherry operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Check Cherry with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Check Cherry using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Check Cherry tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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.

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. Google ADK 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