Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the CircleCI in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Let your AI check CircleCI: pipelines, workflows and jobs, failed tests and artifacts, Insights metrics and flaky tests, contexts and variable names, and start pipelines or rerun and cancel workflows after you confirm.
Try asking
Example prompts for CircleCI
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → CircleCI, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
CircleCI + ChatGPT
Let your AI check CircleCI: pipelines, workflows and jobs, failed tests and artifacts, Insights metrics and flaky tests, contexts and variable names, and start pipelines or rerun and cancel workflows after you confirm.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
CIRCLECI_TOKEN
Step 1 — Get credentials
- Sign in to CircleCI at
https://app.circleci.comand open User Settings → Personal API Tokens (https://app.circleci.com/settings/user/tokens). - Click Create New Token, give it a name and copy it. Newer tokens start with
CCIPAT_. Project API tokens from the project settings do not work with API v2. - Paste the token into
CIRCLECI_TOKENas it is, without a prefix, and install the connector. It is sent in theCircle-Tokenheader to circleci.com only. - Check the setup with
circleci_get_current_user, thencircleci_list_collaborationsto see the organizations you belong to.
Who sees what: the token has the same rights as your CircleCI user in every organization you belong to. Share the MCP server only with people who may see those builds.
Project slugs: most tools need the project slug shown in Project Settings → Overview. GitHub OAuth and Bitbucket Cloud projects use gh/<org>/<repo> or bb/<workspace>/<repo> (for example gh/acme/web-app); GitHub App and GitLab projects use circleci/<organization id>/<project id>. Pass the slug with its slashes as it is.
Starts builds and stops running work, so the AI asks first: circleci_trigger_pipeline starts a new pipeline on a branch or tag. It needs a definition id from circleci_list_pipeline_definitions, which in turn needs the project id from circleci_get_project, and it is not available for GitLab projects. circleci_rerun_workflow reruns a workflow as a new workflow: all jobs, only from the failed job onward, or the jobs you choose. circleci_cancel_workflow stops a running workflow, and jobs that have not started will not run. Starting and rerunning use credits and run whatever the config does, deploy jobs included; cancelling can leave a deployment half done. Before each of them the AI tells you the project, branch, workflow or jobs and waits for your yes. No tool is switched off at install, and nothing here deletes projects, contexts or variables.
Finding out why a build failed: circleci_list_pipelines (newest first, optionally for one branch), circleci_get_pipeline by id or circleci_get_pipeline_by_number for the #number in the app; then circleci_list_pipeline_workflows and circleci_list_workflow_jobs to find the failed job and its job number. circleci_get_job gives status, duration, executor, contexts used and the web link. circleci_list_job_tests counts passed, skipped and failed tests and shows every failed test with its message (only for jobs that store test results). circleci_list_job_artifacts lists the stored artifacts with download links, which need the same token. Full step logs are only in the CircleCI app, through the job's web_url.
Trends and flaky tests: circleci_get_workflow_metrics summarizes every workflow of a project over a window from the last 24 hours up to the last 90 days (runs, success rate, duration, credits used, time to recovery), for one branch or all branches. circleci_get_workflow_summary shows one workflow over the last 90 days with its trend against the previous period. circleci_list_flaky_tests lists tests that passed and failed on the same commit, with how often they flaked and the time they wasted. Insights data is refreshed daily, not in real time.
Contexts and variables: circleci_list_contexts needs the organization id from circleci_list_collaborations (or an organization slug such as gh/acme for GitHub OAuth and Bitbucket organizations). circleci_list_context_env_var_names and circleci_list_project_env_var_names return only the names of environment variables, never their values.
Pagination: lists return next_page_token; the AI passes it back as page_token until it is empty.
Common errors: 401: the token is wrong or revoked, or it is a project API token; create a personal API token under User Settings. 404: the project slug is wrong or your user cannot see the project; CircleCI answers 404 rather than 403 for projects outside your access. 429: the rate limit is reached; wait a minute and retry.
The connector does not cover approving held jobs, creating or deleting projects, contexts, environment variables, schedules and webhooks, or reading full job step logs.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in ChatGPT
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
ChatGPT adds MCP servers as plugins on its Plugins page, on the web and on paid plans. Developer mode is no longer needed. In a Business workspace only admins and owners can add one; in Enterprise and Edu an admin can grant the Create plugins with MCPs permission.
- Go to chatgpt.com/plugins, click +, then Add custom MCP server.
- Enter a name, e.g. Name:
CircleCI. - Under Connection, enter the Server URL
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_IDand keep Authentication on OAuth. - Select I understand and want to continue, then Create as a plugin. When ChatGPT asks, sign in to AnythingMCP and allow access.
- Install the new plugin from your personal plugins, then type @ in a chat and pick it.
Available tools
| Tool | What it does |
|---|---|
circleci_get_current_user | Get the CircleCI user the personal API token belongs to: id, login and name |
circleci_list_collaborations | List the organizations the user belongs to: id, name, VCS type and slug (e.g. gh/acme, or circleci/<org-id> for GitHub App and GitLab… |
circleci_get_project | Get a project by slug: name, project id, organization name, slug and id, and the connected repository URL and default branch |
circleci_list_pipeline_definitions | List the pipeline definitions of a project: id, name, description and where the config and code come from |
circleci_list_pipelines | List the pipelines of a project, newest first: id, number, state, branch or tag, commit, trigger, actor, time and setup errors |
circleci_get_pipeline | Get one pipeline by id: number, state, branch or tag, commit, trigger, actor, time and setup errors |
circleci_get_pipeline_by_number | Get one pipeline of a project by its number (the #123 shown in the CircleCI app) |
circleci_list_pipeline_workflows | List the workflows of a pipeline: id, name, status (success, running, failed, on_hold, canceled ...), start and stop time and who started… |
circleci_get_workflow | Get one workflow by id: name, status, pipeline id and number, project, start and stop time, and who started, canceled or errored it |
circleci_list_workflow_jobs | List the jobs of a workflow: id, job number, name, type (build or approval), status, dependencies, start and stop time |
circleci_get_job | Get the details of a job by project and job number: name, status, duration, executor and resource class, parallelism and per-run status… |
circleci_list_job_tests | Summarize the test results a job uploaded with store_test_results: how many passed, were skipped and failed, and for every failed test its… |
circleci_list_job_artifacts | List the artifacts a job stored with store_artifacts: path, node index and download URL |
circleci_get_workflow_metrics | Insights summary for every workflow of a project over a reporting window (default last 90 days): runs, success rate, failed runs, duration… |
circleci_get_workflow_summary | Insights for one workflow: metrics for the last 90 days (runs, success rate, duration, credits, time to recovery) and their trend against… |
circleci_list_flaky_tests | List the project's flaky tests (tests that passed and failed on the same commit): test name, class, file, job and workflow, how often it… |
circleci_trigger_pipeline | Start a new pipeline for a project from a pipeline definition, on a branch or tag |
circleci_rerun_workflow | Rerun a workflow as a new workflow: all jobs, only from the failed job (from_failed), or chosen jobs |
circleci_cancel_workflow | Cancel a running workflow; its running jobs stop and jobs not yet started will not run, which can leave a deployment half done |
circleci_list_contexts | List the contexts (shared sets of environment variables) of an organization: id, name and creation time |
circleci_list_context_env_var_names | List the names of the environment variables in a context, with created and updated time |
circleci_list_project_env_var_names | List the names of a project's environment variables (Project Settings > Environment Variables) with their creation time |
Example prompts
- "Why did the last pipeline on main in gh/acme/web-app fail? Show me the failed job, the failing tests with their messages and the link to the job."
- "Which tests in gh/acme/web-app are flaky, how often did they flake and how much time did they waste?"
- "Compare all workflows of gh/acme/web-app over the last 30 days on all branches: success rate, average duration and credits used."
- "Rerun the deploy workflow of pipeline #1482 from the failed job. Tell me which jobs will run again and ask me before you start it."
- "Start a pipeline on the release/2.4 branch with the parameter deploy set to true. Show me the project, branch and parameters first."
FAQ
Does the free ChatGPT plan work with custom MCP servers? OpenAI documents custom MCP servers for paid plans only; the Free plan is not on its list.
Next steps
Was this guide helpful?
