CircleCI
Consume CircleCI API
About
CircleCI ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.circleci- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- DevOps & Infrastructure · Developer Tools
Overview
CircleCI runs the CI/CD pipelines behind a repository, and this app lets a workflow trigger and watch them instead of only building on push. Start a new pipeline for a project — optionally against a specific branch or tag, with parameters matching the project’s own configuration — then list or fetch the workflows and jobs that ran under it, or cancel one still running.
Pipelines, workflows and jobs form CircleCI’s own hierarchy: a pipeline can spawn several workflows, and each workflow runs a series of jobs, so the actions here follow that structure — list workflows under a pipeline, then jobs under a workflow, then a single job’s details by its project-facing number.
Useful for workflows that need to kick off a build from outside CircleCI’s own triggers, gate a deploy on a pipeline’s outcome, or pull job results into a status page or notification without polling the CircleCI UI. Authentication is a personal API token, since CircleCI has no portable OAuth flow for third-party integrations.
Build with CircleCI
Three routes to the same 8 actions. The Workflow tab is generated from CircleCI's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying CircleCI's real ids.
{
"manifestVersion": "2",
"name": "circleci-example",
"steps": [
{
"id": "job-get",
"uses": {
"app": "io.w6w.circleci",
"action": "job-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"projectSlug": "<projectSlug>",
"jobNumber": "<jobNumber>"
}
}
]
}Here are some of the things you can do
-
Get a job
readjob-get -
List a workflow's jobs
readjob-list -
Get a pipeline
readpipeline-get -
List project pipelines
readpipeline-list -
Trigger a pipeline
performpipeline-trigger
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for CircleCI, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to CircleCI. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "pipeline-trigger",
payload: {
projectSlug: "<value>",
// branch: "<value>",
// tag: "<value>",
// parameters: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action pipeline-trigger --payload '{"projectSlug":"<value>"}'Give an AI agent CircleCI — without giving it CircleCI's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.circleci#job-get",
"input": {
"projectSlug": "<projectSlug>",
"jobNumber": "<jobNumber>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's CircleCI connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
CircleCI's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. CircleCI itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
CircleCI declares its own checks, so its health is a property of the app rather than something the host guesses at.
CircleCI platform status
Atlassian Statuspage rollup for status.circleci.com, with per-component detail. Unauthenticated and unsigned.