Circleci with CrewAI

How to integrate Circleci MCP with CrewAI

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Circleci with TL;DR What is CrewAI What is the Circleci MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Circleci MCP Agent with another framework Explore Other Toolkits FAQ

Connect Circleci without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Circleci to CrewAI 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 CrewAI 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

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex

TL;DR

Here's what you'll learn:

Get a Composio API key and configure your Circleci connection
Set up CrewAI with an MCP enabled agent
Create a Tool Router session or standalone MCP server for Circleci
Build a conversational loop where your agent can execute Circleci operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

Agent Roles: Define specialized agents with specific goals and backstories
Task Management: Create tasks with clear descriptions and expected outputs
Crew Orchestration: Combine agents and tasks into collaborative workflows
MCP Integration: Connect to external tools through Model Context Protocol

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:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Python 3.9 or higher
A Composio account and API key
A Circleci connection authorized in Composio
An OpenAI API key for the CrewAI LLM
Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

bash

pip install composio crewai crewai-tools[mcp] python-dotenv

What's happening:

composio connects your agent to Circleci via MCP
crewai provides Agent, Task, Crew, and LLM primitives
crewai-tools[mcp] includes MCP helpers
python-dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID scopes the session to your account
OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python

import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

What's happening:

CrewAI classes define agents and tasks, and run the workflow
MCPServerHTTP connects the agent to an MCP endpoint
Composio will give you a short lived Circleci MCP URL

Create a Composio Tool Router session for Circleci

python

composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["circleci"])

url = session.mcp.url

What's happening:

You create a Circleci only session through Composio
Composio returns an MCP HTTP URL that exposes Circleci tools

Initialize the MCP Server

python

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )

What's Happening:

Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python

print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")

What's Happening:

Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Circleci and CrewAI:

python

from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

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

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["circleci"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Circleci through Composio's Tool Router. The agent can perform Circleci operations through natural language commands.

Next steps:

Add role-specific instructions to customize agent behavior
Plug in more toolkits for multi-app workflows
Chain tasks for complex multi-step operations

How to build Circleci MCP Agent with another framework

OpenAI Agents SDK

Use Circleci MCP with OpenAI Agents SDK

Claude Agent SDK

Use Circleci MCP with Claude Agent SDK

Claude Code

Use Circleci MCP with Claude Code

Claude Cowork

Use Circleci MCP with Claude Cowork

Codex

Use Circleci MCP with Codex

OpenClaw

Use Circleci MCP with OpenClaw

Hermes

Use Circleci MCP with Hermes

CLI

Use Circleci MCP with CLI

Google ADK

Use Circleci MCP with Google ADK

LangChain

Use Circleci MCP with LangChain

Vercel AI SDK

Use Circleci MCP with Vercel AI SDK

Mastra AI

Use Circleci MCP with Mastra AI

LlamaIndex

Use Circleci MCP with LlamaIndex

Explore Other Toolkits

Supabase

Oauth2Api Key

Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.

Codeinterpreter

No Auth

Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

GitHub

Oauth2

GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.

TOOLKIT MARKETPLACE

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 CrewAI?

Yes, you can. CrewAI 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

Never worry about agent reliability

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

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Circleci MCP with CrewAI

Table of Contents

Connect Circleci without Auth hassles

Introduction

Also integrate Circleci with

TL;DR

What is CrewAI?

What is the Circleci MCP server, and what's possible with it?

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio Tool Router session for Circleci

Initialize the MCP Server

Create a CLI Chatloop and define the Crew

Complete Code

Conclusion

How to build Circleci MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

FAQ

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

Can I use Tool Router MCP with CrewAI?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability