MCP: Buildkite MCP Server
by Buildkite
Buildkite's official MCP server: query pipelines, builds, jobs, logs, test runs and flaky-test data from an agent, over a hosted OAuth endpoint or a self-run binary.
CircleCI's official MCP server: pull build failure logs, hunt flaky tests, validate config, trigger and rerun pipelines, and roll back - in natural language from your IDE.
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
The CircleCI MCP Server puts your CI pipeline where your agent can read it. Instead of tabbing to the CircleCI web app to work out why a build went red, you ask in the editor and the agent fetches the failure logs, the test results and the config guidance it needs to propose a fix.
get_build_failure_logs - detailed failure logs from a buildget_latest_pipeline_status - status of the latest pipeline for a branchget_job_test_results - test metadata and results for a jobfind_flaky_tests - identify flaky tests from execution history (optionally written to a directory via FILE_OUTPUT_DIRECTORY)config_helper - validate a CircleCI config and get guidance on itrun_pipeline - trigger a pipelinererun_workflow - rerun a workflow from the start or from the failed jobrun_rollback_pipeline - trigger a rollback for a projectlist_followed_projects, list_artifacts, list_component_versionsfind_underused_resource_classes - spot jobs paying for more compute than they usedownload_usage_api_data - pull data from the CircleCI Usage APIThe usual setup is npx-based and needs Node.js 18 or newer plus a CircleCI personal API token in CIRCLECI_TOKEN; CIRCLECI_BASE_URL points at your CircleCI instance. A Docker image is available as a fallback. For teams, the project documents a self-managed remote server you deploy once (Kubernetes or Docker) with either per-developer or shared tokens, instead of every engineer running a local copy.
Configuration is documented for Cursor, Windsurf, VS Code Copilot, Claude, Amazon Q Developer (~/.aws/amazonq/mcp.json globally or .amazonq/mcp.json per workspace) and any other MCP-compatible client. Telemetry is described in the README. Apache-2.0 licensed and maintained by CircleCI-Public.
Covered in the Weekly
by Buildkite
Buildkite's official MCP server: query pipelines, builds, jobs, logs, test runs and flaky-test data from an agent, over a hosted OAuth endpoint or a self-run binary.
Microsoft's official MCP server for Azure DevOps - work items, repos, pipelines, wikis, test plans and iterations, reachable from any MCP client in plain language.
Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.
by Currents
Gives coding agents your CI test results from Currents: failed runs, flaky tests, error trends, quarantine rules and Playwright trace evidence.