CircleCI MCP. Monitor builds and deploy code from chat.
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 connects your build system and deployment pipelines to any AI agent. You can query, monitor, or manually trigger software builds—getting detailed status reports on workflows, jobs, and environments without opening a dashboard.
What your AI agents can do
Get job details
Provides detailed information for a specific job within a workflow run.
Get my cci profile
Retrieves basic identity and membership information about the authenticated user.
Get workflow details
Gathers detailed structural information for a specific workflow definition.
List and retrieve detailed information about recent CI/CD pipelines across your accounts.
Manually trigger a new pipeline run for any specific project or branch immediately.
Access detailed structure and status information for entire workflows, including all associated jobs.
Get deep metadata and execution status reports for specific, individual jobs within a workflow.
List shared environment contexts used across your organization to manage sensitive project data.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
CircleCI: 8 Tools for Pipeline Management
These tools let you interact with every part of a CI/CD process, from listing overall pipelines to checking the status of a single job.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using CircleCI on Vinkius019d7570get job details
Provides detailed information for a specific job within a workflow run.
019d7570get my cci profile
Retrieves basic identity and membership information about the authenticated user.
019d7570get workflow details
Gathers detailed structural information for a specific workflow definition.
019d7570list cci contexts
Lists all shared environment contexts used by the organization for securing data.
019d7570list cci pipelines
Retrieves a list of recent and active CI/CD pipelines across various projects.
019d7570list pipeline workflows
Shows all the specific workflows that exist within one given pipeline run.
019d7570list workflow jobs
Lists every individual job associated with a specified workflow.
019d7570trigger cci pipeline
Initiates a brand new pipeline run for an entire project, specifying the branch and target.
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,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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
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.
The dashboard click-fest never ends.
Today, checking on a build means opening CircleCI. You navigate to the project, find the pipeline run, expand it to see all workflows, and then drill down into specific jobs just to check logs. It's three tabs open, six clicks deep, and you’re wasting time copying IDs and pasting them into Slack.
With this MCP, you skip the UI entirely. You tell your agent what you need—like 'Show me all failed deployments in the last week.' The agent handles the navigation and data retrieval using tools like `list_cci_pipelines` and delivers a clean summary right back to you.
Get job details with get_job_details.
Before, if a build failed due to an obscure error, you had to locate the exact job ID from the list view, then navigate to that job's dedicated page just to grab the failure logs. That was tedious and prone to copy-paste errors.
Now, your agent pulls everything together. You ask for details on a specific job, and it returns all metadata and status reports in one clean response. It’s immediate context without leaving the chat.
What you can do with this MCP connector
This connector gives you full control over complex CI/CD processes through natural conversation. Instead of logging into the CircleCI dashboard, your agent handles everything from checking the health of last week's release to manually initiating an emergency build for a specific branch.
Need to know why a deployment failed? You can list recent pipelines and check detailed job metadata instantly. The system tracks shared environment contexts used across projects, so you always have visibility into where sensitive data is being secured during the process. Because complex deployments often require actions in multiple systems—say, checking build status then updating Jira tickets—you can chain this MCP with other services via Vinkius.
This means your agent doesn't just read statuses; it builds an automated sequence of steps across platforms using a single connection point.
Your AI client handles the heavy lifting: listing workflows inside a pipeline or pulling up user profile details to confirm who initiated the last run. It’s all about getting accurate, immediate system status without the manual clicks.
019d7570-3b24-7176-9b8c-c0a9a4e6d27c 
How CircleCI MCP Works
- 1 Subscribe to this MCP and provide your CircleCI Personal API Token.
- 2 Connect the token through your AI client (like Cursor or Claude).
- 3 Ask your agent a natural language question, such as 'Show me the status of my latest deployment job,' and get instant results.
The bottom line is that you treat complex CI/CD operations like talking to a colleague—you just ask, and the system provides the actionable answer.
Who Is CircleCI MCP For?
DevOps Engineers who spend too much time manually checking dashboards. Release Managers needing instant verification of deployment gates. Developers who hate switching between their IDE and a build dashboard to see why their code broke.
Runs automated checks on pipeline health and triggers manual builds when the automated process stalls.
Audits job failures or reviews workflow progress without having to navigate the CircleCI UI.
Verifies release pipeline status and approves manual gates straight from their chat interface during critical deployments.
What Changes When You Connect
- Check build status instantly: Use
list_cci_pipelinesto see the success or failure of your latest deployment without logging into a separate web dashboard. You know exactly where things stand, right here in your chat. - Control deployments on demand: Need to fix an issue? Running
trigger_cci_pipelineallows you to manually start a new pipeline for a specific project and branch with simple conversation prompts. - Deep visibility into failures: If a job fails, don't just see 'Failed.' Use the agent to query
get_job_detailsto pull deep metadata on why that single step broke. You get actionable logs right away. - Understand system structure: Before debugging, use
list_cci_contextsto list shared environments. This helps you confirm which set of variables your deployment process is actually using for sensitive data. - Track dependencies easily: If a pipeline has multiple stages, calling the agent to look up
list_pipeline_workflowsshows you the entire dependency map—which jobs rely on which other components.
Real-World Use Cases
Urgent Hotfix Required
A developer sees a production bug. Instead of manually navigating to the build page, they tell their agent: 'I need a hotfix run for the main branch.' The agent uses trigger_cci_pipeline and reports back the new pipeline ID immediately.
Pre-release Audit
A Release Manager needs to confirm all necessary stages passed. They ask the agent to list recent pipelines, using list_cci_pipelines, confirming that not only did the build succeed but also the specific 'security scan' job reported a passing status.
Debugging Workflow Breakage
A workflow runs but stops prematurely. The engineer asks the agent to check list_workflow_jobs for that pipeline, revealing which specific job (get_job_details) timed out and providing the exact error log.
Checking User Permissions
Before running a sensitive deployment, you ask your agent to use get_my_cci_profile to verify that your current user account still has the required organization membership rights for the target project.
The Tradeoffs
Asking general chat questions
Typing 'What's wrong with my build?' and waiting for a vague answer. The agent can only guess, wasting time.
→
You must use specific tools. Start by running list_cci_pipelines to narrow down the date/project, then query that result using get_workflow_details to pinpoint where the failure occurred.
Over-relying on UI links
Getting a list of jobs from one source, but needing more context than the dashboard provides. The information is fragmented across multiple tabs.
→
Use list_workflow_jobs to get the names, and then follow up with get_job_details using that job name to pull all associated metadata in one conversational flow.
Forgetting context variables
Running a build for Project A but forgetting that the required environment variable only exists in Project B's shared contexts, leading to an obscure failure.
→
Always run list_cci_contexts first. This confirms all available shared environments are known by your agent before you attempt to trigger any deployment.
When It Fits, When It Doesn't
Use this MCP if your job requires coordinating actions across multiple, discrete stages—for example, 'List pipelines,' then check the list_workflow_jobs, and finally use trigger_cci_pipeline for a fix. You need visibility into both historical status and manual intervention points. Don't use it if you simply want to read static documentation about your CI/CD process; that information lives outside of this MCP. If all you need is to verify who owns the repository, then calling get_my_cci_profile is sufficient for a quick check.
Common Questions About CircleCI MCP
How do I check recent pipelines using list_cci_pipelines? +
You simply ask your agent to 'List my last 10 pipelines.' The MCP handles the call, and you get a summary of all projects' build statuses immediately.
Can I manually trigger a pipeline using trigger_cci_pipeline? +
Yes. You tell your agent to 'Trigger a new run for the web-app on the main branch.' The MCP executes this action and gives you the brand new pipeline ID.
What is the difference between list_cci_pipelines and get_workflow_details? +
list_cci_pipelines gives a high-level view of runs over time. get_workflow_details dives deep into the structure—it shows you exactly how one single workflow is defined with its internal jobs.
How do I find out what contexts are available? (list_cci_contexts) +
Use list_cci_contexts. It will list all shared environment variables and data containers your organization has set up, helping you understand the scope of variables used by builds.
What information can I get about a specific job run using `get_job_details`? +
You retrieve detailed status and metadata for any single job execution. This includes seeing the exact exit code, resource usage metrics, and logs that pinpoint why a build failed or succeeded.
How do I map out all jobs within a specific workflow using `list_workflow_jobs`? +
Running list_workflow_jobs returns an exhaustive list of every job defined in a workflow. This lets you check the full scope of the pipeline without needing to trigger or wait for it to run.
I need to verify my user identity and organization role; what does `get_my_cci_profile` do? +
This tool fetches your authenticated user profile details. It confirms who you are, shows your organizational membership, and provides context on the scope of data available to your agent.
If I know my pipeline ID, how do I find all associated workflows using `list_pipeline_workflows`? +
By calling list_pipeline_workflows, you get a list of every workflow that belongs beneath a specific pipeline. This is the first step in understanding the full structural map of your CI/CD process.
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.