# How to integrate Botstar MCP with Google ADK ```json { "title": "How to integrate Botstar MCP with Google ADK", "toolkit": "Botstar", "toolkit_slug": "botstar", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/botstar/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/botstar/framework/google-adk.md", "updated_at": "2026-05-12T10:03:49.150Z" } ``` ## Introduction This guide walks you through connecting Botstar to Google ADK using the Composio tool router. By the end, you'll have a working Botstar agent that can open live chat widget for new visitor, update user profile in current chat session, retrieve chatbot application id for setup through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Botstar account through Composio's Botstar MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Botstar with - [OpenAI Agents SDK](https://composio.dev/toolkits/botstar/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/botstar/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/botstar/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/botstar/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/botstar/framework/codex) - [OpenClaw](https://composio.dev/toolkits/botstar/framework/openclaw) - [Hermes](https://composio.dev/toolkits/botstar/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/botstar/framework/cli) - [LangChain](https://composio.dev/toolkits/botstar/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/botstar/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/botstar/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/botstar/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/botstar/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Botstar account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Botstar - Build an agent that connects to Botstar through MCP - Interact with Botstar 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 Botstar MCP server, and what's possible with it? The Botstar MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Botstar account. It provides structured and secure access to your chatbot operations, so your agent can perform actions like managing live chat sessions, updating user details, retrieving app parameters, and sending data between webviews and your bot—all on your behalf. - Live chat session control: Programmatically open, close, or reinitialize the Botstar live chat widget to manage user interactions in real time. - Automated user profile updates: Let your agent update user details and profile attributes during an active chatbot conversation for a more personalized experience. - Webview data exchange: Seamlessly send responses from webviews back to the chatbot or retrieve parameters passed from the bot to your webview for dynamic content handling. - Custom callback registration: Set up onOpen and onClose event handlers so your agent can trigger actions whenever users interact with the chat window. - Application ID and configuration retrieval: Fetch essential Botstar application IDs and parameters for smooth widget initialization and advanced bot customization. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `BOTSTAR_CREATE_BOT` | Create Bot | Tool to create a new bot in BotStar. Use when you need to create a new bot instance with a specific name. | | `BOTSTAR_CREATE_BOT_ATTRIBUTE` | Create Bot Attribute | Tool to create a new bot attribute in BotStar. Bot attributes are global variables for a bot and support multilingual values. Use when you need to define custom data fields for your bot. | | `BOTSTAR_CREATE_CMS_ENTITY` | Create CMS Entity | Tool to create a CMS entity in BotStar with a name and optional fields. Use when you need to define a new content structure with custom fields supporting various data types. | | `BOTSTAR_CREATE_ENTITY_FIELDS` | Create Entity Fields | Tool to create entity field(s) in BotStar CMS. Supports multiple field types including text, multiple_values, single_option, multiple_options, image, date, and entity. Use when you need to add new fields to an existing entity. | | `BOTSTAR_CREATE_ENTITY_ITEM` | Create Entity Item | Tool to create a new entity item in BotStar CMS. Use when adding items to a CMS entity with custom field values. | | `BOTSTAR_CREATE_USER_ATTRIBUTES` | Create User Attributes | Tool to create custom user attributes in BotStar. Use when you need to define new custom attributes for users with specified field name and type. | | `BOTSTAR_DELETE_BOT_ATTRIBUTE` | Delete Bot Attribute | Tool to delete a bot attribute by ID. Use when you need to remove a custom attribute from a bot. | | `BOTSTAR_DELETE_CMS_ENTITY` | Delete CMS Entity | Tool to delete a CMS entity by ID. Use when you need to remove an entity from the bot's content management system. | | `BOTSTAR_DELETE_ENTITY_FIELDS` | Delete Entity Fields | Tool to delete entity field(s) from a CMS entity. Use when you need to remove fields from a CMS entity by their unique names. | | `BOTSTAR_DELETE_ENTITY_ITEM` | Delete Entity Item | Tool to delete an entity item from a CMS entity. Use when you need to remove a specific item from a bot's CMS entity. | | `BOTSTAR_GET_BOT` | Get Bot | Tool to get your bot by bot ID. Use when you need detailed bot information including ID, name, and team name. | | `BOTSTAR_GET_BOT_APP_ID` | Get BotStar Application IDs | Tool to retrieve the BotStar application ID (`appId`). Use when initializing or reinitializing the live chat widget. | | `BOTSTAR_GET_CMS_ENTITY` | Get CMS Entity | Tool to get a specific CMS entity by ID. Returns entity details including fields configuration. Use when you need to retrieve metadata about a CMS entity structure. | | `BOTSTAR_GET_ENTITY_ITEM` | Get Entity Item | Tool to retrieve a specific item from a CMS entity with all field values. Use when you need to get detailed information about a single entity item. | | `BOTSTAR_LIST_BOT_ATTRIBUTES` | List Bot Attributes | Tool to get all bot attributes from BotStar. Returns array of bot attributes with id, name, desc, value, and data_type. Use when you need to retrieve or inspect all attributes configured for a bot. | | `BOTSTAR_LIST_BOTS` | List Bots | Tool to get your list of bots. Use when you need to retrieve all bots associated with your account. Returns an array of bots with their id, name, and team_name. | | `BOTSTAR_LIST_CMS_ENTITIES` | List CMS Entities | Tool to retrieve all CMS entities for a bot. Use when you need to access entity definitions, field configurations, or available entity schemas. | | `BOTSTAR_LIST_ENTITY_ITEMS` | List Entity Items | Tool to retrieve all entity items with pagination support. Use when you need to list CMS entity items, with optional filtering by name and status. | | `BOTSTAR_LIVECHAT_BOOT` | Livechat boot | Tool to reinitialize the live chat widget with provided data. Use after initial load to reset or update widget configuration. | | `BOTSTAR_LIVECHAT_CLOSE` | Close BotStar Livechat Widget | Tool to hide the live chat window. Use when the chat widget is configured in livechat or popup mode. | | `BOTSTAR_BOTSTAR_LIVECHAT_ON_CLOSE` | BotStar LiveChat onClose Callback | Tool to register a callback when the chat window is closed. Use after the widget is initialized. Example prompt: "Register an onClose handler that logs 'Goodbye!' to the console." | | `BOTSTAR_LIVECHAT_ON_OPEN` | Livechat on open | Tool to register a callback when the chat window is opened. Use after widget initialization. | | `BOTSTAR_LIVECHAT_OPEN` | Livechat open | Tool to show the live chat window. Use after the widget has been bootstrapped with BotStarApi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup'). | | `BOTSTAR_LIVECHAT_UPDATE` | Livechat update | Tool to update user details on the current live chat session. Use when you need to modify user profile attributes during an active conversation. | | `BOTSTAR_PUBLISH_BOT` | Publish Bot to Live | Tool to publish a bot to live. Use when you need to deploy changes to the production environment. | | `BOTSTAR_UPDATE_BOT_ATTRIBUTE` | Update Bot Attribute | Tool to update a bot attribute in BotStar. Use when you need to modify the description or value of a bot attribute with optional multilingual support. | | `BOTSTAR_UPDATE_CMS_ENTITY` | Update CMS Entity | Tool to update a CMS entity in BotStar. Use when you need to modify the name or configuration of an existing CMS entity. | | `BOTSTAR_UPDATE_ENTITY_FIELDS` | Update Entity Fields | Tool to update entity field(s) in BotStar CMS. Use when you need to modify the name or options of existing fields. | | `BOTSTAR_UPDATE_ENTITY_ITEM` | Update Entity Item | Tool to update a CMS entity item in BotStar. Use when you need to modify the name, status, or custom field values of an entity item. | | `BOTSTAR_WEBVIEW_GET_PARAMETER` | Get BotStar Webview Parameter | Tool to retrieve a parameter value passed from the BotStar chatbot to the webview. Use inside onChatBotReady after your page loads in modal mode with bs:input meta tags. | | `BOTSTAR_WEBVIEW_SEND_RESPONSE` | Webview send response | Tool to send data from the webview back to the BotStar chatbot. Use when you need to transmit responses or custom outputs from an open webview. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Botstar MCP server is an implementation of the Model Context Protocol that connects your AI agent to Botstar. It provides structured and secure access so your agent can perform Botstar operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 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 ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - 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. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Botstar via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables 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 ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate 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 ```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.") ``` ### 6. Create Composio client and Tool Router session 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 ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["botstar"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent 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 ```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 Botstar operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent 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 ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```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=["botstar"], ) 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 Botstar operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Botstar with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Botstar using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Botstar 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. ## How to build Botstar MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/botstar/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/botstar/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/botstar/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/botstar/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/botstar/framework/codex) - [OpenClaw](https://composio.dev/toolkits/botstar/framework/openclaw) - [Hermes](https://composio.dev/toolkits/botstar/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/botstar/framework/cli) - [LangChain](https://composio.dev/toolkits/botstar/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/botstar/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/botstar/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/botstar/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/botstar/framework/crew-ai) ## Related Toolkits - [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools. - [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations. - [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates. - [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates. - [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations. - [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code. - [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls. - [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources. - [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates. - [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows. - [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment. - [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality. - [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster. - [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment. - [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support. - [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach. - [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback. - [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Botstar MCP? With a standalone Botstar MCP server, the agents and LLMs can only access a fixed set of Botstar tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Botstar and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Google ADK? 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 Botstar tools. ### Can I manage the permissions and scopes for Botstar while using Tool Router? Yes, absolutely. You can configure which Botstar 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 Botstar data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)