All servers / CircleCI (official)
CircleCI (official)
CircleCI builds and configs.
Deprecated by its publisherScore 68 out of 100. Tested 2026-11-17 on package version 0.20.0. Package: @circleci/mcp-server-circleci · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 12 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 2 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (26.5 seconds including download)
- Tools offered: 13
- Last published: 2026-08-06
- Weekly downloads (npm): 23,710
- License: Apache-2.0 · Direct dependencies: 8
Notes
- Its publisher has marked this package deprecated: "Deprecated: use CircleCI's hosted MCP server or CircleCI CLI MCP instead. See https://circleci.com/docs/guides/toolkit/circleci-mcp-overview/"
Tools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_build_failure_logs0 of 1 parameter describedThis tool helps debug CircleCI build failures by retrieving failure logs. CRITICAL REQUIREMENTS: 1. Large Log Handling: - If you expect large logs or want the full output, provide outputDir. The full logs will be written to a file and the path returned.
find_flaky_tests0 of 1 parameter describedThis tool retrieves information about flaky tests in a CircleCI project. The agent receiving this output MUST analyze the flaky test data and implement appropriate fixes based on the specific issues identified. CRITICAL REQUIREMENTS: 1. Truncation Handling
get_latest_pipeline_status0 of 1 parameter describedThis tool retrieves the status of the latest pipeline for a CircleCI project. It can be used to check pipeline status, get latest build status, or view current pipeline state. Common use cases: - Check latest pipeline status - Get current build status - View
get_job_test_results0 of 1 parameter describedThis tool retrieves test metadata for a CircleCI job. PRIORITY USE CASE: - When asked "are tests passing in CI?" or similar questions about test status - When asked to "fix failed tests in CI" or help with CI test failures - Use this tool to check if tests a
config_helper0 of 1 parameter describedThis tool helps analyze and validate and fix CircleCI configuration files. Parameters: - params: An object containing: - configFile: string - The full contents of the CircleCI config file as a string. This should be the raw YAML content, not a file path. Example us
run_pipeline0 of 1 parameter describedThis tool triggers a new CircleCI pipeline and returns the URL to monitor its progress. Input options (EXACTLY ONE of these THREE options must be used): Option 1 - Project Slug and branch (BOTH required): - projectSlug: The project slug obtained from listFollow
list_followed_projects0 of 1 parameter describedThis tool lists all projects that the user is following on CircleCI. Common use cases: - Identify which CircleCI projects are available to the user - Select a project for subsequent operations - Obtain the projectSlug needed for other CircleCI tools
rerun_workflow0 of 1 parameter describedThis tool is used to rerun a workflow from start or from the failed job. Common use cases: - Rerun a workflow from a failed job - Rerun a workflow from start Input options (EXACTLY ONE of these TWO options must be used): Option 1 - Workflow ID: - workflowId: The ID of
download_usage_api_data0 of 1 parameter described⚠️ **MANDATORY: The handler will REJECT any call that does not include BOTH outputDir and originalUserMessage. These parameters are REQUIRED for all tool calls.** ⚠️ **MANDATORY OUTPUT DIRECTORY SELECTION FOR AI AGENTS:** 1. If the project root (workspace root)
find_underused_resource_classes0 of 1 parameter describedAnalyzes a CircleCI usage data CSV file to find jobs/resource classes with average or max CPU/RAM usage below a given threshold (default 40%). This helps identify underused resource classes that may be oversized for their workload. Required parameter: - csvFileP
run_rollback_pipeline0 of 1 parameter describedRun a rollback pipeline for a CircleCI project. This tool guides you through the full rollback process, adapting to the information you provide and prompting for any missing details. **Initial Requirements:** - You need either a `projectSlug` (from `listFollowedProj
list_component_versions0 of 1 parameter describedThis tool lists all versions for a CircleCI component. It guides you through a multi-step process to gather the required information and provides lists of available options when parameters are missing. **Initial Requirements:** - You need either a `projectSlug` (
list_artifacts0 of 1 parameter describedThis tool retrieves the list of artifacts produced by a CircleCI job. Common use cases: - List all artifacts generated by a specific job - Find download URLs for build artifacts (binaries, reports, logs, etc.) - Check what artifacts were produced by a pipeli
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.