How to Use the CircleCI MCP in Cline

Q: How do I get my own user details from CircleCI?

Just ask Cline to run the getmycciprofile tool. It will query the CircleCI API with your token and return your user ID and name. It's a good way to confirm which account your agent is acting as.

Tell Cline to run a build in CircleCI. It handles everything from triggering the pipeline to reporting the results, right in VS Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CircleCI MCP to Cline

Create your Vinkius account to connect CircleCI to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup CircleCI with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run a full build cycle from one command

Cline connects to this MCP server to give you direct control over your CI/CD process. Tell it, "Run the tests for this feature branch on CircleCI." Cline uses the `trigger_cci_pipeline` tool to start the build, then monitors it without you having to do anything else. Because Cline is an autonomous agent, it can see the build through to the end. It periodically checks the status using `get_workflow_details` and `list_workflow_jobs`. When the pipeline finishes, it gives you a simple pass or fail notification, all inside VS Code.

Drill down into any pipeline or job

When a build breaks, you need answers fast. Instead of opening CircleCI in a browser, just ask Cline, "Show me the jobs for the last failed pipeline." It uses `list_cci_pipelines` and `list_pipeline_workflows` to find the right run, then pulls the job list. You can go deeper and ask for specific details with `get_job_details`. It's a huge time-saver compared to digging through the web UI, and it's all possible because of the MCP connection. You stay focused on your code, not on managing tabs.

Configure projects with this MCP Server

Setting up a new project's CI/CD often involves checking what shared resources are available. With this server, you can just ask Cline to `list_cci_contexts`. It gives you a direct list of all available contexts in your organization so you can configure your `.circleci/config.yml` correctly the first time. This simple check avoids common errors where a pipeline fails because it can't access the necessary environment variables or secrets. It's about getting the setup right from the start, directly from your editor.

Setup guide

Set up CircleCI MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type circleci-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest CircleCI refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "circleci-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect CircleCI now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about CircleCI MCP in Cline

You can give Cline a multi-step goal like, "After I push this commit, trigger the CircleCI pipeline and let me know when it's done." Cline will stage the commit, push, and then use the `trigger_cci_pipeline` tool to start the build.

Yes, absolutely. If a pipeline fails, ask Cline, "Which job failed in the last build?" It will use tools like `list_pipeline_workflows` and `list_workflow_jobs` to trace the failure down to the exact job and report back.

Cline understands context and can chain commands intelligently. A script just runs preset steps. You can tell Cline, "Find the error in the last staging deployment," and it will figure out how to use the available CircleCI tools to get you an answer, which is something a simple script can't do.

Just ask Cline to run the `get_my_cci_profile` tool. It will query the CircleCI API with your token and return your user ID and name. It's a good way to confirm which account your agent is acting as.

No, Cline doesn't store it. The CircleCI MCP server processes requests ephemerally. Your auth token is managed by the Vinkius platform and is never exposed directly to the agent or logged. The server only handles CircleCI pipeline, job, and context metadata for each request.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript