CircleCI MCP. Manage every build, job, and workflow from your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
CircleCI MCP Server lets your AI agent manage your entire CI/CD lifecycle. Use it to list recent pipelines, check job statuses, trigger new builds, and audit project workflows without opening the CircleCI dashboard.
It gives you full control over your software delivery process directly from your chat client.
What your AI agents can do
Get job details
Retrieves specific metadata and execution status for a single job run.
Get my cci profile
Gets information about the user who authenticated with the server.
Get workflow details
Retrieves detailed information for a specific workflow.
List recent CI/CD pipelines and retrieve deep status details for individual jobs and entire workflows.
Trigger a new pipeline run for a specific project and branch immediately.
List all shared environment contexts and retrieve metadata about your organization's structure.
Get detailed information about a specific workflow, including all associated jobs.
Retrieve your personal user profile and list your organization memberships.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
CircleCI MCP Server: 8 Tools for Pipeline Job Management
These tools let your agent interact with your CircleCI account. They let you list pipelines, check job status, and trigger builds using natural language prompts.
019d7570get job details
Retrieves specific metadata and execution status for a single job run.
019d7570get my cci profile
Gets information about the user who authenticated with the server.
019d7570get workflow details
Retrieves detailed information for a specific workflow.
019d7570list cci contexts
Lists all shared environment contexts available for an organization.
019d7570list cci pipelines
Lists the most recent CI/CD pipelines for your accounts.
019d7570list pipeline workflows
Lists all workflows that exist within a specific pipeline run.
019d7570list workflow jobs
Lists all individual jobs that belong to a specified workflow.
019d7570trigger cci pipeline
Manually starts a new pipeline run for a specified project and branch.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with CircleCI, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Your AI client lets you manage your whole CI/CD process without touching the CircleCI dashboard. You can handle everything—from checking build status to kicking off a release—just by talking to your agent.
Audit Build Status
You can check the most recent CI/CD pipelines with list_cci_pipelines. For deep status checks, you get specific metadata and execution status for a single job run using get_job_details. You can also pull detailed info for an entire workflow using get_workflow_details, and list all individual jobs that belong to a specified workflow with list_workflow_jobs.
You'll find all workflows inside a specific pipeline run by calling list_pipeline_workflows.
Manually Start Builds
Need a build running right now? You can trigger a new pipeline run immediately for any project and branch using trigger_cci_pipeline.
Map Project Dependencies
To see what environments your projects rely on, you can list all shared environment contexts available for your organization using list_cci_contexts. This helps you map out your project's structure.
View Workflow Structure
When you know which workflow you need to check, get_workflow_details gives you the full rundown. You can list all the individual jobs that belong to a workflow using list_workflow_jobs.
Get User Info
Your agent can get your personal user profile details with get_my_cci_profile and list your organization memberships.
How CircleCI MCP Works
- 1 Subscribe to the server and provide your CircleCI Personal API Token (find this in User Settings).
- 2 Your AI client uses natural language to specify the target project, branch, or pipeline ID.
- 3 The agent calls the appropriate tool (e.g.,
list_cci_pipelines) and returns the structured data and status directly in the chat.
The bottom line is you manage complex, multi-step deployment processes using simple conversation.
Who Is CircleCI MCP For?
The DevOps Engineer who's tired of clicking through dashboards at 2 am. This is for developers and operations teams who need to audit build failures, verify release status, or manually kick off a fix—all without leaving their chat interface. It cuts out the manual dashboard navigation.
Monitor pipeline health, list recent runs, and trigger manual builds using plain language.
Audit job failures and review workflow progress without needing to open the full CircleCI dashboard.
Verify release pipeline status and approve manual gates directly from the chat window.
Manage shared environment contexts and environment variables across different projects.
What Changes When You Connect
- Full Audit Trail: Instead of manually navigating job logs, you can call
get_job_detailsto get the exact metadata and status of a failed build step. Knowing the failure point instantly saves time. - Zero-Click Builds: Don't wait for a commit. Use
trigger_cci_pipelineto manually start a new pipeline run for a project and branch, right when you need it, without opening the UI. - Context Awareness: Need to know what environment variables are available?
list_cci_contextslists all shared contexts, helping you verify if your project has the right secrets before deployment. - Workflow Mapping: Don't guess how a project runs. Use
list_pipeline_workflowsto map out every workflow within a specific pipeline, giving you a clear structure of the release process. - Immediate Status Checks: Need to know if the latest push succeeded?
list_cci_pipelinesgives you a quick list of recent runs and their success status, all in one response. - User Verification: Need to confirm which teams you belong to?
get_my_cci_profileretrieves your user profile and organization membership details instantly.
Real-World Use Cases
Debugging a Production Failure
A developer sees a build fail. Instead of logging into CircleCI, they tell their agent: 'Check the job details for the 'test' job in the last failed pipeline.' The agent uses get_job_details and immediately provides the status and metadata, letting the developer jump straight to the fix.
Preparing a Hotfix Release
The Release Manager needs to test a patch immediately. They prompt the agent: 'Trigger a new pipeline for the staging environment on the main branch.' The agent executes trigger_cci_pipeline, and the process starts instantly, giving the manager confidence before deployment.
Reviewing a Complex Release Flow
The Ops Engineer wants to understand the release process for the 'billing' service. They ask the agent to use list_cci_pipelines to see the last few runs, then list_pipeline_workflows to map the specific steps, and finally list_workflow_jobs to see the build steps.
Checking Environment Readiness
The Infra Team needs to verify if a new service can connect to secure data. They ask the agent to run list_cci_contexts to see all available shared contexts, ensuring all necessary variables are in place before proceeding with the deployment.
The Tradeoffs
Manual Dashboard Jumping
Opening CircleCI, finding the project, clicking the pipeline, finding the workflow, then scrolling through job logs to find the failure point.
→
Tell your agent to use list_cci_pipelines to find the ID, then list_workflow_jobs to drill down, and finally get_job_details for the exact failure point. It keeps you in the chat.
Assuming Contexts Exist
Trying to run a build that fails because the required environment variable isn't set, and spending an hour digging into old documentation to find the correct context name.
→
Use list_cci_contexts first. It shows you every shared context available in the organization, confirming what variables you can actually use.
Over-Relying on UI Buttons
Waiting for a commit push to trigger a test build, even when you know the code is ready and needs to be tested immediately.
→
Use trigger_cci_pipeline to manually start the run. You control the start time, not the commit schedule.
When It Fits, When It Doesn't
Use this if your job involves auditing, monitoring, or controlling software releases—any time you need to know 'what happened' or 'what needs to happen next' within your CI/CD flow. You need to check statuses, list history, or force a build. Don't use it if you just need to read documentation or manage repository code directly; those are source control tools. You must use this if you need to read the current status of jobs or pipelines, or if you need to manually initiate a run. If you only need basic user info, get_my_cci_profile handles that, but for any operational task, this server is required.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by CircleCI. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking pipeline status shouldn't feel like a forensic audit.
Today, checking a build's health means clicking into the CircleCI dashboard, finding the project, navigating to the pipeline list, and then clicking on the specific run. If the build failed, you're deep in a series of tabs and dropdowns, manually hunting for the job name and the failure code. It's slow and requires too much context switching.
With the CircleCI MCP Server, you just ask your agent: 'What's the status of the last web-app build?' The agent calls `list_cci_pipelines`, reads the result, and gives you a clean answer, telling you exactly which pipeline failed and why. You stay in your chat, and the data comes to you.
CircleCI MCP Server: Trigger builds and audit jobs from chat
Manual triggers used to require running `circleci ci project --branch main` in a terminal, or relying on a developer to push a dummy commit just to kick off the test run. It was clunky and required switching environments.
Now, you just ask your agent: 'Kick off a new pipeline for the API project on the main branch.' The agent uses `trigger_cci_pipeline` and starts the process instantly. You get immediate confirmation and a new pipeline ID.
Common Questions About CircleCI MCP
How do I check the status of my last five pipelines using list_cci_pipelines? +
The agent automatically calls list_cci_pipelines and returns a list of the most recent runs. The response summarizes the status (success/fail) and provides the necessary links or IDs for deeper investigation.
What is the difference between list_workflow_jobs and get_job_details? +
list_workflow_jobs gives you a list of all jobs belonging to a workflow. get_job_details requires a specific job ID and provides the full, granular metadata and execution status for that single job.
Can I trigger a pipeline without knowing the project ID? +
You don't have to. You simply tell the agent the project name and the branch name, and the agent uses the correct parameters for trigger_cci_pipeline.
Does list_cci_contexts help me find my API keys? +
No, it lists the shared environment contexts. These are the containers for variables (like API keys) that your project uses, helping you verify if the necessary variables are set up for the build.
What if I need to check my own user profile with get_my_cci_profile? +
How do I use get_workflow_details to check the status of a specific workflow? +
You pass the workflow ID to the get_workflow_details tool. This retrieves the full status, including which jobs ran and if they succeeded or failed. It's useful for seeing the overall health of a specific process.
Can I use list_pipeline_workflows to see what jobs are in a pipeline? +
Yes, list_pipeline_workflows lists all workflows tied to a specific pipeline ID. You then use list_workflow_jobs with the resulting workflow ID to see all the jobs within it.
What is the purpose of list_cci_contexts when setting up the server? +
list_cci_contexts shows shared environment contexts for your organization. You use these contexts to ensure your AI agent has access to secure, shared project data, which is critical for multi-team builds.
Can I trigger a build for a specific branch through the agent? +
Yes! Use the trigger_cci_pipeline tool. You need to provide the project slug (e.g., gh/org/repo) and the branch name. The agent will instruct CircleCI to start the pipeline immediately.
How do I see why a specific job failed? +
Use the get_job_details tool with the project slug and job number. Your agent will fetch the execution status and metadata, which often points to the cause of failure.
Where do I find my CircleCI API Token? +
Log in to CircleCI, go to User Settings -> Personal API Tokens. You can generate and copy a new token from there.
Multi-server workflows that include CircleCI MCP
MCP Servers That Diagnose CI Failures First
Your CI pipeline has been red for 6 hours and the team keeps pushing to the same branch , nobody knows the failure is a flaky infrastructure test, not their code
Track Engineering Metrics Using MCP Servers
Merge request velocity measured, pipeline success rates tracked, cycle time calculated, team metrics published , build your DORA dashboard without a BI tool
Track Technical Debt Per Pull Request via MCP
Build failures analyzed, code complexity measured, tech debt cataloged, remediation prioritized , track what you owe your codebase
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Railway
Equip your AI with direct access to your Railway infrastructure — manage projects, deployments, services, and environment variables.
Spider
High-performance Rust-powered web scraping and crawling — scrape, crawl, and search up to 100K+ pages/second with built-in anti-bot protection.
Grafana k6 Cloud (Load Testing)
Manage load tests via k6 Cloud — run tests, monitor performance metrics, and audit thresholds.
You might also like
Pando
Share large files and folders securely with clients using branded transfer portals and download analytics for creative teams.
Chaport
Manage live chat and customer messaging via Chaport — track visitors, send messages, and monitor operator status directly from any AI agent.
Kandji
Manage Apple devices, blueprints, and security via Kandji MDM API.