How to integrate Circleci MCP with LangChain

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

Get started for freeGet a demo
Circleci logoCircleci
Api Key

Circleci is a leading continuous integration and delivery platform for automating code builds, tests, and deployments. It helps teams ship quality software faster by streamlining DevOps workflows.

65 Tools

Introduction

This guide walks you through connecting Circleci to LangChain 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 LangChain 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 SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Circleci project to Composio
  • Create a Tool Router MCP session for Circleci
  • Initialize an MCP client and retrieve Circleci tools
  • Build a LangChain agent that can interact with Circleci
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

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 step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

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.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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 your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Circleci functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Circleci tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['circleci']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Circleci tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Circleci tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "circleci-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Circleci MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Circleci tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Circleci related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['circleci']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "circleci-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Circleci related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Circleci through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Circleci action and event your agent gets out of the box.

Create Context

Tool to create a new context in CircleCI.

Create Context (GraphQL)

Tool to create a new CircleCI context using the GraphQL API.

Create Context Restriction

Tool to create a context restriction in CircleCI.

Create Organization Orb Allowlist

Tool to create a new URL Orb allow-list entry for an organization.

Create Organization Project

Tool to create a new project within a CircleCI organization.

Create Organization Group

Tool to create a group in an organization.

Create Project Environment Variable

Tool to create a new environment variable for a CircleCI project.

Create Usage Export Job

Tool 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 Restriction

Tool to delete a context restriction by its ID.

Delete Namespace and Related Orbs

Tool to delete a CircleCI registry namespace and all its associated orbs.

Delete Namespace Alias

Tool to remove a namespace alias by name in CircleCI.

Delete Organization Orb Allowlist Entry

Tool to remove an entry from the organization's URL orb allow-list.

Delete Organization Group

Tool to delete a group from a CircleCI organization.

Delete Project

Tool to delete a CircleCI project and its settings.

Delete Project Environment Variable

Tool to delete an environment variable from a CircleCI project.

Get Context

Tool to retrieve a context by its unique ID.

Get Current User

Tool to retrieve information about the currently authenticated user.

Get Flaky Tests

Tool to get flaky tests for a project.

Get Job Artifacts

Retrieves artifacts (output files like test results, logs, build binaries, reports) produced by a CircleCI job.

Get Job Details

Tool to fetch details of a specific job within a project.

Get Orb Details

Tool to query detailed information about a CircleCI orb using the GraphQL API.

Get Orb Version

Tool to retrieve detailed information about a specific CircleCI orb version via GraphQL.

Get Organization

Tool to retrieve organization details from CircleCI using GraphQL query.

Get Organization Group

Tool to retrieve a group in an organization.

Get Pipeline Config

Tool to fetch pipeline configuration by ID.

Get Pipeline Definition

Tool to retrieve a pipeline definition by project and definition ID.

Get Project

Tool to retrieve a CircleCI project by its slug.

Get Project Workflows

Tool to get summary metrics for all workflows of a project.

Get Test Metadata

Tool to fetch test metadata for a specific job.

Get Usage Export Job

Tool to retrieve a usage export job by organization ID and job ID.

Get User Information

Tool to retrieve information about a CircleCI user by their unique ID.

Get Workflow Summary

Tool to get metrics and trends for a workflow.

List Context Environment Variables

Tool to list all environment variables for a specific context.

List Insights Branches

Tool to get all branches for a project from CircleCI Insights.

List Insights Summary

Tool to get summary metrics with trends for the entire organization and for each project.

List Namespace Orbs

Tool to list orbs in a CircleCI registry namespace with pagination support.

List Orb Categories

Tool to retrieve all CircleCI orb categories with pagination support.

List Orbs

Tool to list CircleCI orbs with pagination support via GraphQL API.

List Organization Groups

Tool to list all groups in a CircleCI organization.

List Pages Summary

Tool to get summary metrics and trends for a project across its workflows and branches.

List Pipeline Definitions

Tool to list all pipeline definitions for a specific project.

List Pipelines

Tool to get a list of pipelines for an organization.

List Pipelines for Project

Tool to list all pipelines for a specific project.

List Project Environment Variables

Tool to list all environment variables for a CircleCI project.

List Project Schedules

Tool to list all schedules for a specific project.

List Self-Hosted Runners

List self-hosted runners in CircleCI.

List User Collaborations

Tool to retrieve organizations where the authenticated user has access.

List Workflows by Pipeline ID

Tool to list all workflows associated with a specific pipeline.

List Workflows Jobs Workflows

Tool to get summary metrics for a project workflow's jobs.

List Workflows Test Metrics

Tool to get test metrics for a project's workflows.

Query Context

Tool to retrieve a CircleCI context by its UUID using GraphQL API.

Query Namespace Exists

Tool to determine if a namespace exists in the CircleCI registry.

Query Orb Category ID

Tool to fetch the unique category ID for a CircleCI orb category by its name.

Query Orb Exists

Tool to check if an orb exists in CircleCI registry and retrieve its privacy status.

Query Orb ID

Tool to fetch an orb's ID and optionally its namespace ID by orb name.

Query Orb Latest Version

Tool to fetch the latest published version of a CircleCI orb.

Query Orb Source

Tool to retrieve source code of a specific CircleCI orb version via GraphQL.

Query Plan Metrics

Tool 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 Namespace

Tool to rename a CircleCI namespace by its UUID identifier.

Store Environment Variable

Tool to store an environment variable in a CircleCI context using GraphQL mutation.

Trigger Pipeline

Triggers a new CI/CD pipeline run for a specified CircleCI project.

Upsert Context Environment Variable

Tool to add or update an environment variable in a CircleCI context.

Validate Orb Config

Tool to validate CircleCI orb YAML configuration using the orbConfig GraphQL query.

FRAMEWORKS

How to build Circleci MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Circleci MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Circleci MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Circleci MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Circleci MCP with Claude Cowork

Codex logo

Codex

Use Circleci MCP with Codex

OpenClaw logo

OpenClaw

Use Circleci MCP with OpenClaw

Hermes logo

Hermes

Use Circleci MCP with Hermes

CLI logo

CLI

Use Circleci MCP with CLI

Google ADK logo

Google ADK

Use Circleci MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Circleci MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Circleci MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Circleci MCP with LlamaIndex

CrewAI logo

CrewAI

Use Circleci MCP with CrewAI

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Circleci.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

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

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

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's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

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

Nirman Dave
Nirman Dave
CEO, Zams

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

Ryan Yu
Ryan Yu
Founder, Extra Thursday

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

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

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.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies