AI Tool Profile

CircleCI MCP Server: Hosted vs CLI, Pricing, Risks, and Evaluation

CircleCI’s hosted and CLI-integrated MCP servers let compatible AI assistants inspect CI runs, logs, tests and artifacts and, when authorized, perform workflow or broader CircleCI operations.

Before you buy

Best for: Developers and platform teams that want CI evidence inside an AI coding session and can separate diagnostic access from mutating or administrative credentials.

Price: MCP code plus applicable CircleCI and model usage charges

Included: MCP access to supported CircleCI workflow and build information.

Main limits: Hosted and CLI/server modes have different credentials and exposure. Underlying compute credits, seats and agent-model charges remain separate.

What Kingy showed: Related coverage: CircleCI MCP Server Guide: What It Does, Pricing, Use Cases, and Alternatives. This review does not treat that article as a new test of this exact model, plan or current release.

Buying details checked 2026-10-23 with region and currency stated above. Historical demonstrations and the broader fact ledger keep their own dates.

Check official plans · See the demonstration and disclosure · Compare these workflows

Source recheck dueSoftwareProfile source check: 2026-07-28

Coverage describes this profile, not a product score or a current price guarantee.

Company: Not yet reviewed
Primary job: Not yet reviewed
Audience: Not yet reviewed

Evidence: Source-backed; coverage expanding
Latest source check: October 23, 2026

See all tracked product factsPricing, platforms, dependencies, data claims, regions, and timeline

Sources and checks

Coverage: 1 of 87 tracked fields currently verified
Sources: 1

Source-check dates apply to the tracked facts. Editorial updates elsewhere on this page may have a different date.

Plans and pricing units

Not yet structured in this Kingy record.

Where it runs

Availability: Not yet reviewed

Stack and integrations

Model / provider dependencies: Not yet reviewed
Integrations: Not yet reviewed

Data and regions

Vendor data-use claim: Not yet reviewed
Vendor retention claim: Not yet reviewed
Regions: Not yet reviewed

Launch and latest material update

Launch: Not yet reviewed
Latest material update: Not yet reviewed

Review history

CircleCI MCP Server: Hosted vs CLI, Pricing, Risks, and Evaluation — Product Facts updatedOctober 23, 2026
Kingy published an approved change to this Product Facts record.
View published revision

Who should consider it

Developers and platform teams that want CI evidence inside an AI coding session and can separate diagnostic access from mutating or administrative credentials. CircleCI’s hosted and CLI-integrated MCP servers let compatible AI assistants inspect CI runs, logs, tests and artifacts and, when authorized, perform workflow or broader CircleCI operations.

Plan, price and billing scope

MCP code plus applicable CircleCI and model usage charges. MCP access to supported CircleCI workflow and build information. Prices use the currency and billing term stated here. Where a numeric rate, region or current entitlement could not be verified, it remains explicit; no checkout was completed.

Limits that affect the decision

Hosted and CLI/server modes have different credentials and exposure. Underlying compute credits, seats and agent-model charges remain separate.

What the existing evidence shows

Related coverage: CircleCI MCP Server Guide: What It Does, Pricing, Use Cases, and Alternatives. This review does not treat that article as a new test of this exact model, plan or current release. Product coverage; original publication date and evidence scope retained. Read the related article.

Sources and buying-review date

Buying review completed October 23, 2026. This is a source-based buying assessment. No paid product test, new generation, checkout or performance benchmark was performed. Vendor descriptions and historical examples remain distinct from independently measured results. The date does not renew the broader canonical fact ledger.

Check the official offer · Compare related options

Earlier profile, sources and dates

This older record retains its original scope. Current buying qualifications above take precedence where terms have changed.

Kingy verdict: CircleCI’s current MCP story is more useful—and more complicated—than the original launch record suggests. The standalone Node server from April 2025 is deprecated. New evaluations should compare CircleCI’s hosted MCP server for focused run diagnosis with the broader MCP interface built into the CircleCI CLI, then put explicit confirmation around every mutating or administrative action.

What the current product is

CircleCI now documents two independent MCP routes. The hosted server runs at CircleCI and connects over HTTPS using OAuth 2.0 or a personal API token. Its curated tool set follows the hierarchy of a CI run: list runs, inspect workflows and jobs, read failed-step logs, review test results and artifacts, then rerun or cancel a workflow. The CLI MCP runs locally and inherits credentials from the CircleCI CLI.

The CLI route is much broader. CircleCI says it exposes the CLI surface for configuration authoring and validation, projects and contexts, environment variables, policies, runner resources, code signing, deployments, cache operations and direct API calls. That extra reach makes it useful for platform engineering, but it also changes the risk profile. A diagnostic assistant and an administrative assistant should not receive the same credential or confirmation policy simply because both speak MCP.

The deprecation matters

CircleCI’s April 9, 2025 changelog announced a standalone open-source server. The current changelog and product documentation mark that implementation deprecated or in maintenance mode and direct new users to the hosted server or the CLI-integrated MCP. Existing CircleCI Server installations may still need the standalone package, but its repository should not be presented as the primary forward path.

This transition is also a migration check. Teams should inventory old npx configurations and long-lived personal tokens before adding a new server. Otherwise, an assistant can retain two overlapping CircleCI connections with different versions and credentials, making tool selection and audit attribution harder to reason about.

Pricing and operational cost

CircleCI does not publish a separate MCP add-on price on the reviewed pages. Access depends on the underlying CircleCI organization, plan, compute credits, users, storage and any applicable add-ons. The standalone repository is public, but open source does not make the CircleCI service or the agent’s model usage free. Estimate cost from the workloads the assistant can trigger, especially reruns, evaluation pipelines and administrative commands.

How Kingy would evaluate it

Start with hosted MCP and a read-oriented task pack: locate the latest failed run on a branch, identify the failed step, retrieve only the relevant log range, list failing tests and name available artifacts. Reconcile every answer with the CircleCI interface or API. Then test access boundaries across two projects, a fork, a private artifact and a user whose permissions were just revoked.

Evaluate mutations separately. Require the assistant to state the target workflow, branch, current status, intended action and expected cost before a rerun or cancellation. For the CLI MCP, use a dedicated low-privilege identity and block context, environment-variable, runner-token, signing and policy changes until each has an approved use case. Record the CircleCI actor and MCP client for every action.

Kingy reviewed CircleCI’s current product page, MCP overview, launch changelog, public repository and pricing material. We did not connect a CircleCI organization, inspect live logs or execute a workflow.

Primary sources

The Kingy Brief

AI changes, original tests and one practical thing to try. Fridays at 09:00 Vancouver time.

Free · Double opt-in · Unsubscribe anytime

Signup help and newsletter schedule

Signup form provided by Beehiiv. After submitting, check your inbox for "Confirm your subscription to The Kingy Brief" and open its confirmation link. Check Spam or Promotions if you cannot find it.

Fridays at 09:00 Vancouver time: source-checked AI changes, original tests and one practical thing to try. We skip a week when there is not enough verified material. Free. Unsubscribe anytime.

Alternatives

View alternatives page

Tool Links

Official site Latest recorded launch Company profile

Launch History

AI Developer Tools Launch date: April 9, 2025 Added: July 9, 2026 Last verified: July 28, 2026

CircleCI MCP Server

CircleCI announced its original open-source MCP Server for AI-assisted access to pipeline, workflow, job, log, test and artifact context. CircleCI now marks that standalone server deprecated and directs…

Recheck due Free: No API: Yes Open: Yes

Developer-friendlyGitHub tractionTraction signal

Launch readiness: 7.0 / 10
Demo evidence: Not scored yet
Creator-story fit: Not scored yet

Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale: 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by: Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date: Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-28.
Confidence and missing data: Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness: Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes: Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

The CircleCI MCP launch established a useful bridge from CI evidence to coding assistants, but the original standalone implementation is no longer the forward…

View launch View tool profile Source Suggest correction

Submit a related launch Get a Launch Visibility Score Sponsor Kingy AI Estimate creator ROI Contact Kingy AI