Can AI agents automate CircleCI?
CircleCI · saas · ci-cddeveloper-tools
CircleCI is automatable today through a documented REST API. This record is the hosted CircleCI CI/CD product, not Jenkins, GitLab CI, GitHub Actions, or Azure DevOps. API v2 accepts personal API tokens only; project tokens are not supported on v2. Callers send the token as Authorization Bearer (recommended) or a Circle-Token header. Documented v2 categories include context, insights, user, pipeline, job, workflow, webhook, OIDC token management, policy management, project, usage, and schedule, with next_page_token pagination and HTTP 429 plus Retry-After rate limits. API v3 is served under /api/v3 on https://circleci.com and is where new capabilities land; v3 requires Authorization Bearer and rejects query-parameter tokens. OAuth 2.0 Dynamic Client Registration with authorization-code and mandatory PKCE can mint a 90-day personal API token without a client secret. Outbound webhooks POST JSON for workflow-completed and job-completed events. CircleCI documents a first-party hosted MCP server at https://mcp.circleci.com/v1/mcp (OAuth2 or personal API token) and an MCP server built into the CircleCI CLI. Vendor docs mark both MCP surfaces as preview; the earlier npx @circleci/mcp-server-circleci local server is deprecated. The official CLI v1 is also preview. It supports circleci auth login, --json and --jq output, and circleci mcp start. No official language SDK was established from the opened API pages. iPaaS connectors were not opened. Computer-use viability is unassessed. API scores 8 and is the best path. MCP and CLI stay at 6 because both are vendor preview.
Best path today: api · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | restpersonal-api-token coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: official |
| Integrations | unknown | |
| CLI | yes | |
| Extensibility | yes | webhooks: True |
| Data access | export: api-json · import: unknown | |
| RPA / UI automation | unknown | web-dom No repeatable UI probe was run. CircleCI's REST API, outbound webhooks, official CLI, hosted MCP, and CLI MCP cover practical pipeline automation without browser control.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 8 | 6 | — | 6 | — | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-09-02 |
license | declared | source | 2026-09-02 |
modalities.api.exists | declared | source | 2026-09-02 |
modalities.api.kinds[0] | declared | source | 2026-09-02 |
modalities.api.auth[0] | declared | source | 2026-09-02 |
modalities.api.coverage | declared | source | 2026-09-02 |
modalities.mcp.first_party | declared | source | 2026-09-02 |
modalities.cli.exists | declared | source | 2026-09-02 |
modalities.extensibility.webhooks | declared | source | 2026-09-02 |
modalities.data_access.export[0] | declared | source | 2026-09-02 |
modalities.agent_docs.llms_txt | declared | source | 2026-09-02 |
verdict.scores.api | declared | source | 2026-09-02 |
verdict.scores.mcp | declared | source | 2026-09-02 |
verdict.scores.cli | declared | source | 2026-09-02 |
freshness.watch[0].url | declared | source | 2026-09-02 |
freshness.watch[1].url | declared | source | 2026-09-02 |
freshness.watch[2].url | declared | source | 2026-09-02 |
freshness.watch[3].url | declared | source | 2026-09-02 |
Related tools
Other products in this database that share a category with CircleCI.
Last verified 2026-09-02 · volatility high · JSON record