How to integrate CrowTerminal MCP with Google ADK

This guide walks you through connecting CrowTerminal to Google ADK using the Composio tool router. By the end, you'll have a working CrowTerminal agent that can debug failing docker build command, automate repeated git cleanup commands, recall yesterday's terminal troubleshooting notes through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a CrowTerminal account through Composio's CrowTerminal MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

CrowTerminal logoCrowTerminal
Api KeyBasic

CrowTerminal is an AI-powered command line assistant with memory and automation for developers. Use it to speed up terminal work, keep context, and automate repetitive dev tasks.

27 Tools

Introduction

This guide walks you through connecting CrowTerminal to Google ADK using the Composio tool router. By the end, you'll have a working CrowTerminal agent that can debug failing docker build command, automate repeated git cleanup commands, recall yesterday's terminal troubleshooting notes through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a CrowTerminal account through Composio's CrowTerminal MCP server.

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

Also integrate CrowTerminal with

TL;DR

Here's what you'll learn:
  • Get a CrowTerminal account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for CrowTerminal
  • Build an agent that connects to CrowTerminal through MCP
  • Interact with CrowTerminal 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 CrowTerminal MCP server, and what's possible with it?

The CrowTerminal MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your CrowTerminal account. It provides structured and secure access so your agent can perform CrowTerminal operations on your behalf.

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 CrowTerminal 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=["crowterminal"],
)

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 CrowTerminal 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 CrowTerminal 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=["crowterminal"],
)

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 CrowTerminal operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate CrowTerminal 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 CrowTerminal action and event your agent gets out of the box.

Analyze Agent Engagement

Tool to analyze engagement correlation for every field in your agent's markdown.

Compare Agent Markdown

Tool to compare your agent's markdown directly with all stored versions.

Create Webhook

Tool to register a new webhook for receiving real-time event notifications from CrowTerminal.

Delete Webhook

Tool to delete an existing webhook registration.

Get BYOK Platform Intelligence

Tool to get algorithm insights for TikTok, Instagram, and YouTube without client-specific context.

Get Client Memory Changelog

Retrieve human-readable change history for a client's memory.

Get Client Memory Pattern

Tool to track a specific field over time for trend analysis.

Get Components Status

Tool to get detailed status of each CrowTerminal service component.

Get Data Types

Tool to retrieve valid data types for ingestion across platforms.

Get Recent Incidents

Tool to retrieve list of recent incidents from CrowTerminal with duration and affected components.

Get Platform Intelligence

Tool to retrieve algorithm insights for TikTok, Instagram, and YouTube.

Get Sandbox Client

Tool to get mock client data for testing in the sandbox environment.

Get Sandbox Memory

Tool to retrieve mock memory/skill data for testing purposes.

Get Service Status

Retrieve CrowTerminal service status including overall health, component metrics, and uptime data.

Get Status History

Tool to get 7-day uptime data points ready for visualization and charting.

Get Uptime Data

Tool to retrieve historical uptime data for CrowTerminal agents.

Bulk Ingest Analytics Data

Tool to bulk ingest up to 50 analytics data points at once to CrowTerminal.

Ingest Analytics Data

Tool to ingest platform analytics data from TikTok Studio, Instagram Insights, or YouTube Analytics.

List Webhooks

Tool to list all registered webhooks for the authenticated agent.

Ping CrowTerminal Service

Tool to check CrowTerminal service availability via a simple ping endpoint.

Bulk Read Memory

Tool to read memory for multiple clients at once (up to 50).

Register Agent

Tool to self-register a new agent and obtain an API key.

Sandbox Engagement Analysis

Tool to run mock engagement analysis in the CrowTerminal sandbox environment.

Test Webhook

Tool to test a webhook URL by sending a test payload.

Update Webhook

Tool to update an existing webhook configuration in CrowTerminal.

Validate Proposed Changes

Tool to validate proposed changes against historical data before updating memory.

Validate Sandbox

Tool to mock validation endpoint for testing in sandbox.

FAQ

Frequently asked questions

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

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

Start with CrowTerminal.It takes 30 seconds.

Managed auth, hosted MCP servers, and every CrowTerminal tool your agent needs.Free to start.

Start building