Skip to content
Vinkius

CircleCI Connector for AI agents.

8 live capabilities

Manage CI/CD pipelines and trigger automated builds from your agent.

Live agent request CircleCI / Connector

Waiting for input…

AI Agent

Why people use CircleCI

CircleCI for CI/CD Pipeline Management

This Connector changes that. You just ask your agent for the status or to trigger a run. It pulls the data and puts it right in front of you. You get a continuous workflow where the AI handles the navigation and you just make the decisions.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get direct, conversational control over your CircleCI builds without leaving your primary workspace.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Debugging a failed build

    A developer asks why the last build failed.

  2. Real-world use case 02

    Manual production deployment

    A release manager tells the agent to start a build on the main branch.

  3. Real-world use case 03

    Onboarding and permissions

    A new team member asks for their account details.

Complete set · 8capabilities

The complete CircleCI capability set.

These are the exact actions your AI can choose when you ask it to work with CircleCI.

Capability set01 / 02

01—04

4 capabilities in this set.

Part of 8 available through CircleCI.

  1. 01 Capability

    Get my cci profile

    Get your account details and membership info. This helps you confirm which user is currently authenticated.

  2. 02 Capability

    Get workflow details

    Pull specific data for a single workflow. Use this to see the structure of a specific pipeline.

  3. 03 Capability

    List cci contexts

    See all shared contexts for an organization. This is useful for checking available environment variables.

  4. 04 Capability

    List workflow jobs

    See every job inside a specific workflow. Use this to audit the full sequence of a build.

Capability set02 / 02

05—08

4 capabilities in this set.

Part of 8 available through CircleCI.

  1. 05 Capability

    List cci pipelines

    List your most recent CI/CD pipelines. This gives you a quick look at recent activity across projects.

  2. 06 Capability

    Trigger cci pipeline

    Start a new pipeline run for a project. You can use this to kick off builds on specific branches.

  3. 07 Capability

    Get job details

    Get the execution status and metadata for a specific job. This helps you find exactly where a build failed.

  4. 08 Capability

    List pipeline workflows

    List all workflows tied to a specific pipeline. This helps you see the different paths a pipeline can take.

Set up in minutes

One URL. Then ask CircleCI to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use CircleCI from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_RYNFniMxh53CKeYToBM2UNUbXRz4n2cftwtxDiON/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it CircleCI, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable CircleCI for the conversation.

Where the request belongs

Work CircleCI can move forward.

Built around the request

For DevOps engineers and release managers who spend half their day clicking through build logs or manually triggering pipelines across dozens of projects.

01

DevOps Engineer

Checks pipeline health and triggers manual builds during production incidents using natural language.

02

Software Developer

Audits failed jobs and reviews workflow progress while staying in their IDE.

03

Release Manager

Verifies release status and approves manual gates via a chat interface.

Bring your own AI

Change the model, client or framework. Keep CircleCI connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about CircleCI.

The practical details behind the request, access and result.

Can I use the CircleCI MCP to trigger builds?

Yes. You can ask your agent to start a new pipeline for any project and branch. It will handle the request and return the new pipeline ID for you.

How do I see why my build failed using this Connector?

Just ask your agent for the status of a specific job. It will pull the execution metadata and tell you exactly where the process stopped.

Does the CircleCI MCP work with Cursor and Claude?

Yes. Since it's an Connector, it works with any compatible client like Claude, Cursor, Windsurf, or VS Code once connected via Vinkius.

Can I check my user profile with CircleCI MCP?

Yes. Your agent can retrieve your account details, membership information, and other profile data directly from CircleCI.

Can I see all the jobs in a specific workflow?

Yes. You can ask your agent to list all jobs within a workflow. It will show you every step in the sequence and their current statuses.

Can I manage shared contexts with CircleCI MCP?

Yes. You can ask your agent to list the shared contexts for your organization to see what environment variables are currently available.

Can I trigger a build for a specific branch through the agent?

Yes! Use the trigger_cci_pipeline capability. 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 capability 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.

One connection away

Give your agent a direct line to CircleCI.

Connect CircleCI once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available