How to integrate DeployHQ MCP with Google ADK

GET STARTED FOR FREE
Framework Integration Gradient
DeployHQ Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting DeployHQ to Google ADK using the Composio tool router. By the end, you'll have a working DeployHQ agent that can trigger a deployment for project x, list all deployments for project y, get status of last deployment through natural language commands.

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

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

TL;DR

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

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

Supported Tools & Triggers

Tools
Delete CommandTool to delete a command from a specified project.
Delete ProjectTool to delete a project from DeployHQ.
Delete Build Cache FileTool to delete an existing build cache file from a project.
Delete Excluded File RuleTool to delete an existing excluded file rule from a project.
Delete Server GroupTool to delete a server group from a project using the DeployHQ API.
Delete TemplateTool to delete a template by its unique permalink.
Get ProjectsTool to retrieve all projects from DeployHQ account.
Get ProjectTool to view an existing project in DeployHQ.
Get Project Build Known HostsTool to list all known hosts within a project using DeployHQ API.
Get Project CommandsTool to retrieve all SSH commands configured for a project.
Get Project Config FilesTool to retrieve a list of all config files in a DeployHQ project.
Get Project DeploymentsTool to retrieve a paginated list of all deployments in a project.
Get Project Excluded FilesTool to list all excluded files within a project template.
Get Config FileTool to view a specific config file in a DeployHQ project.
Get Excluded FileTool to view a specific excluded file in a DeployHQ project.
Get Server GroupTool to view a specific server group in a DeployHQ project.
Get Project RepositoryTool to view repository details for a specific project in DeployHQ.
Get Repository BranchesTool to view all available branches in the connected repository for a project.
Get Repository Commit InfoTool to view detailed information about a specific revision in a project's connected repository.
Get Latest Repository RevisionTool to view the latest remote revision of your repository.
Get Recent Commits and TagsTool to view up to 15 most recent revisions and up to 15 most recent tags in a specific branch.
Get Project Scheduled DeploymentsTool to retrieve all upcoming scheduled deployments for a project.
Get Project Server GroupsTool to retrieve all server groups configured for a project.
Get Project ServersTool to retrieve all servers configured for a project.
Get TemplatesTool to retrieve all templates from DeployHQ account.
Get Public TemplateTool to retrieve a specific public template from DeployHQ.
Get Public TemplatesTool to retrieve publicly available deployment templates from DeployHQ.
Update ProjectTool to update project settings in DeployHQ.
Update Build Cache FileTool to update an existing build cache file in a project.
Update Build CommandTool to update an existing build command in a project.
Update Language VersionTool to update the version of a language in a project's build environment.
Update Project CommandTool to update an existing SSH command in a project.
Update Config FileTool to update an existing config file in a DeployHQ project.
Update Excluded FileTool to update an existing excluded file rule in a project.
Update Project RepositoryTool to update repository configuration for a project in DeployHQ.
Update Server GroupTool to update an existing server group in a DeployHQ project.
Update TemplateTool to update an existing template in DeployHQ.
Create ProjectTool to create a new project in DeployHQ.
Generate AI Deployment OverviewTool to generate an AI-powered deployment overview for a revision range.
Create Build Cache FileTool to create a new build cached file within a project.
Create Build CommandTool to create a new build command for a project in DeployHQ.
Create Project Build Known HostTool to create a new known host in a project using DeployHQ API.
Create SSH CommandTool to create a new SSH command for a project in DeployHQ.
Create Config FileTool to create a new config file in a DeployHQ project.
Create Config File DeploymentTool to create a new config file deployment for a project.
Create Excluded FileTool to add a new excluded file to a project.
Abort DeploymentTool to abort a currently running deployment.
Add Project RepositoryTool to add repository details to a project in DeployHQ.
Create Server GroupTool to create a new server group for automated deployments in a DeployHQ project.
Create ServerTool to create a new server configuration in a DeployHQ project.
Create TemplateTool to create a new template in DeployHQ.
Update Project SettingsTool to update settings of an existing DeployHQ project.
Edit Build Cache FileTool to edit an existing build cache file within a project.
Edit Build CommandTool to edit an existing build command within a template in DeployHQ.
Edit SSH CommandTool to edit an existing SSH command in a DeployHQ project.
Edit Config FileTool to edit an existing config file within a project.
Edit Excluded FileTool to edit an existing excluded file rule within a project.
Update Excluded FileTool to update an existing excluded file rule in a project.
Update Project RepositoryTool to update repository details for an existing project in DeployHQ.
Update Server GroupTool to update a server group in a DeployHQ project using the API.
Edit TemplateTool to edit an existing template in DeployHQ.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

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

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.

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 DeployHQ via MCP
  • python-dotenv loads environment variables

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

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

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

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

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

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 DeployHQ 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

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 DeployHQ 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=["deployhq"],
)

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

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate DeployHQ 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 DeployHQ MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use DeployHQ MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use DeployHQ MCP with Claude Agent SDK

LangChain

LangChain

Use DeployHQ MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use DeployHQ MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use DeployHQ MCP with Mastra AI

LlamaIndex

LlamaIndex

Use DeployHQ MCP with LlamaIndex

CrewAI

CrewAI

Use DeployHQ MCP with CrewAI

Claude Code

Claude Code

Use DeployHQ MCP with Claude Code

Codex

Codex

Use DeployHQ MCP with Codex

FAQ

What are the differences in Tool Router MCP and DeployHQ MCP?

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

Can I manage the permissions and scopes for DeployHQ while using Tool Router?

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free