Verification & Sources

Evidence state: Recheck due
Source links: 5
Freshness: Needs recheck: checked July 28, 2026
Last updated: July 28, 2026

What this evidence state means

Definition: The claim was previously checked, but its review window expired or a material change may have invalidated it.
Required provenance: The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
Owner: Kingy freshness queue owner and assigned editorial reviewer
Freshness rule: This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
Disputes and corrections: Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.

Key source checks

Official site Source 2 Source 3 Source 4 Source 5

Suggest a correction

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

One consequential launch, one pricing, limit, or shutdown change, one hands-on test, one exact prompt or Test Pack, and one try / watch / skip verdict.

Free · Choose your subjects · Double opt-in · Unsubscribe anytime

Form not showing? Subscribe on Beehiiv.

Tool Links

Official site Latest launch profile 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

Clear use caseDeveloper-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