How to integrate Circleci MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Circleci logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Circleci to Google ADK using the Composio tool router. By the end, you'll have a working Circleci agent that can trigger a new pipeline on main branch, list all pipelines for backend service, get test results from last successful build through natural language commands.

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

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

Also integrate Circleci with

TL;DR

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

The Circleci MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Circleci account. It provides structured and secure access to your Circleci projects and pipelines, so your agent can trigger builds, fetch job artifacts, monitor workflows, and analyze test results on your behalf.

  • Automated pipeline triggering and management: Let your agent start new builds for specific branches or tags, enabling continuous integration workflows without manual intervention.
  • Workflow and job status monitoring: Ask your agent to fetch detailed information about jobs and workflows, including status, timing, and execution environment, to stay on top of your CI/CD processes.
  • Artifact and test result retrieval: Have the agent collect job artifacts or extract comprehensive test metadata and failure messages for easier debugging and reporting.
  • Pipeline and runner insights: Get your agent to list all pipelines for a project or enumerate available self-hosted runners, making it simple to manage and audit your Circleci resources.
  • User and configuration access: Retrieve user profile details or fetch pipeline YAML configurations as needed for documentation, troubleshooting, or workflow optimization.

Supported Tools & Triggers

Tools
Create ContextTool to create a new context in CircleCI.
Create Context (GraphQL)Tool to create a new CircleCI context using the GraphQL API.
Create Context RestrictionTool to create a context restriction in CircleCI.
Create Organization Orb AllowlistTool to create a new URL Orb allow-list entry for an organization.
Create Organization ProjectTool to create a new project within a CircleCI organization.
Create Organization GroupTool to create a group in an organization.
Create Project Environment VariableTool to create a new environment variable for a CircleCI project.
Create Usage Export JobTool to create a usage export job for a CircleCI organization.
Delete Context (GraphQL)Tool to delete a CircleCI context by its UUID using GraphQL API.
Delete Context RestrictionTool to delete a context restriction by its ID.
Delete Namespace and Related OrbsTool to delete a CircleCI registry namespace and all its associated orbs.
Delete Namespace AliasTool to remove a namespace alias by name in CircleCI.
Delete Organization Orb Allowlist EntryTool to remove an entry from the organization's URL orb allow-list.
Delete Organization GroupTool to delete a group from a CircleCI organization.
Delete ProjectTool to delete a CircleCI project and its settings.
Delete Project Environment VariableTool to delete an environment variable from a CircleCI project.
Get ContextTool to retrieve a context by its unique ID.
Get Current UserTool to retrieve information about the currently authenticated user.
Get Flaky TestsTool to get flaky tests for a project.
Get Job ArtifactsRetrieves artifacts (output files like test results, logs, build binaries, reports) produced by a CircleCI job.
Get Job DetailsTool to fetch details of a specific job within a project.
Get Orb DetailsTool to query detailed information about a CircleCI orb using the GraphQL API.
Get Orb VersionTool to retrieve detailed information about a specific CircleCI orb version via GraphQL.
Get OrganizationTool to retrieve organization details from CircleCI using GraphQL query.
Get Organization GroupTool to retrieve a group in an organization.
Get Pipeline ConfigTool to fetch pipeline configuration by ID.
Get Pipeline DefinitionTool to retrieve a pipeline definition by project and definition ID.
Get ProjectTool to retrieve a CircleCI project by its slug.
Get Project WorkflowsTool to get summary metrics for all workflows of a project.
Get Test MetadataTool to fetch test metadata for a specific job.
Get Usage Export JobTool to retrieve a usage export job by organization ID and job ID.
Get User InformationTool to retrieve information about a CircleCI user by their unique ID.
Get Workflow SummaryTool to get metrics and trends for a workflow.
List Context Environment VariablesTool to list all environment variables for a specific context.
List Insights BranchesTool to get all branches for a project from CircleCI Insights.
List Insights SummaryTool to get summary metrics with trends for the entire organization and for each project.
List Namespace OrbsTool to list orbs in a CircleCI registry namespace with pagination support.
List Orb CategoriesTool to retrieve all CircleCI orb categories with pagination support.
List OrbsTool to list CircleCI orbs with pagination support via GraphQL API.
List Organization GroupsTool to list all groups in a CircleCI organization.
List Pages SummaryTool to get summary metrics and trends for a project across its workflows and branches.
List Pipeline DefinitionsTool to list all pipeline definitions for a specific project.
List PipelinesTool to get a list of pipelines for an organization.
List Pipelines for ProjectTool to list all pipelines for a specific project.
List Project Environment VariablesTool to list all environment variables for a CircleCI project.
List Project SchedulesTool to list all schedules for a specific project.
List Self-Hosted RunnersList self-hosted runners in CircleCI.
List User CollaborationsTool to retrieve organizations where the authenticated user has access.
List Workflows by Pipeline IDTool to list all workflows associated with a specific pipeline.
List Workflows Jobs WorkflowsTool to get summary metrics for a project workflow's jobs.
List Workflows Test MetricsTool to get test metrics for a project's workflows.
Query ContextTool to retrieve a CircleCI context by its UUID using GraphQL API.
Query Namespace ExistsTool to determine if a namespace exists in the CircleCI registry.
Query Orb Category IDTool to fetch the unique category ID for a CircleCI orb category by its name.
Query Orb ExistsTool to check if an orb exists in CircleCI registry and retrieve its privacy status.
Query Orb IDTool to fetch an orb's ID and optionally its namespace ID by orb name.
Query Orb Latest VersionTool to fetch the latest published version of a CircleCI orb.
Query Orb SourceTool to retrieve source code of a specific CircleCI orb version via GraphQL.
Query Plan MetricsTool to query plan metrics including credit usage by project and organization for a date range.
Remove Context Environment Variable (GraphQL)Tool to remove an environment variable from a CircleCI context using GraphQL API.
Rename NamespaceTool to rename a CircleCI namespace by its UUID identifier.
Store Environment VariableTool to store an environment variable in a CircleCI context using GraphQL mutation.
Trigger PipelineTriggers a new CI/CD pipeline run for a specified CircleCI project.
Upsert Context Environment VariableTool to add or update an environment variable in a CircleCI context.
Validate Orb ConfigTool to validate CircleCI orb YAML configuration using the orbConfig GraphQL query.

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

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

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

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

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

Conclusion

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

Key takeaways:

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

FAQ

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

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

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

Yes, absolutely. You can configure which Circleci 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 Circleci 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.