How to integrate Circleci MCP with Claude Code

Manage your Circleci directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

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

Manage your Circleci directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Circleci with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Circleci to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Circleci via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Circleci) for even more tool search precision. It's secure and reliable.

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, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Circleci account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['circleci'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http circleci-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Circleci. This URL will be used to connect Claude Code to Circleci.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Circleci
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Circleci MCP to Claude Code

bash
claude mcp add --transport http circleci-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (circleci-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Circleci MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your circleci-composio entry in the list
  • This confirms that Claude Code can now access Circleci tools

If everything is wired up, you should see your circleci-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Circleci

The first time you try to use Circleci tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Circleci
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Circleci authorization flow
  • Return to the terminal and start using Circleci through Claude Code

Once authenticated, you can ask Claude Code to perform Circleci operations in natural language. For example:

  • "Trigger a new pipeline on main branch"
  • "List all pipelines for backend service"
  • "Get test results from last successful build"

Complete Code

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

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['circleci'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http circleci-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Circleci with Claude Code using Composio's MCP server. Now you can interact with Circleci directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Circleci operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Circleci operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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.

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. Claude Code 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