Compared · CI/CD
Best MCP servers for CI/CD
5 entries in the AgentTask Atlas catalog fit ci/cd. They are not ranked by a score: the table lists active entries first, then by how many clients document a setup, and each row ends with our one-line verdict on when to pick it. Official sources last checked 2026-10-26.
- No credentials needed: none — every entry here needs some account, key or connection string.
- Offers a hosted/remote option: GitLab MCP Server, GitHub MCP Server, Azure DevOps MCP Server, Buildkite MCP Server, CircleCI MCP Server (hosted)
- Most documented clients: Cursor (5), Claude Code (5), Claude Desktop (5), VS Code (5), GitHub Copilot (3), Codex (3).
| Name | Type | Credentials | License | Clients | Tools · tokens | Verdict |
|---|---|---|---|---|---|---|
| GitLab MCP Server GitLab | MCP server | Required | Not stated for the MCP server (built into GitLab) | 12 | — | Pick it to work with GitLab merge requests, issues and pipelines from the agent; limit toolsets with the X-Gitlab-Enabled-Mcp-Server-Toolsets header for narrower access. |
| GitHub MCP Server GitHub | MCP server | Required | MIT | 9 | 46 · ~11,131 | Pick it for issues, PRs and Actions from the agent; limit toolsets or use read-only mode for review tasks. |
| Azure DevOps MCP Server Microsoft | MCP server | Required | MIT | 8 | — | Pick it when your team lives in Azure DevOps and you want the agent to read work items, PRs and pipeline logs; start with X-MCP-Readonly and narrow toolsets, since writes act as you. |
| Buildkite MCP Server Buildkite | MCP server | Required | MIT | 7 | — | Pick it to let the agent investigate failed Buildkite builds and logs; use the read-only endpoint unless you want it to retry jobs or start builds. |
| CircleCI MCP Server (hosted) CircleCI | MCP server | Required | Not stated (hosted service) | 6 | — | Pick it to ask why the last CircleCI run failed and get the logs and failing tests in your editor; review reruns and cancels before approving, they change real CI state. |
Tools · tokens: measured tool count and context cost of each server's tool definitions; see the MCP tool budget for method and all servers.
Install notes
- GitLab MCP Server
- Add the HTTP server `https://gitlab.com/api/v4/mcp` (Self-Managed/Dedicated: `/api/v4/mcp` on your instance URL). Claude Code: `claude mcp add -s user --transport http GitLab https://gitlab.com/api/v4/mcp`; clients without HTTP support use `npx mcp-remote` (see docs). official docs ↗Credentials: OAuth access token with the `mcp` scope (dynamic client registration or a pre-registered OAuth app), or a fine-grained personal access token with the MCP tool resource; legacy, project and group tokens are rejected. Access must be allowed for the top-level group (GitLab.com) or the instance. · Maintenance: Built into GitLab (generally available since GitLab 19.5, all tiers); MCP server docs last changed 2026-10-17 in gitlab-org/gitlab; no separate release
- GitHub MCP Server
- Remote: add https://api.githubcopilot.com/mcp/ in your client; local: Docker image ghcr.io/github/github-mcp-server (see README). official docs ↗Credentials: GitHub OAuth (remote server) or a Personal Access Token (GITHUB_PERSONAL_ACCESS_TOKEN). · Maintenance: Release v2.0.3 on 2026-10-21; last commit 2026-10-22
- Azure DevOps MCP Server
- Remote (VS Code): add `{"servers":{"ado-remote-mcp":{"url":"https://mcp.dev.azure.com/{organization}","type":"http"}}}` to .vscode/mcp.json; Claude Code: `claude mcp add --transport http ado https://mcp.dev.azure.com/{organization} --client-id {client-id} --callback-port 3118`. Local: `npx -y @azure-devops/mcp {organization}` (optionally `-d core work work-items`). official docs ↗Credentials: Microsoft Entra ID (OAuth) for the remote server; Cursor and Claude Code need a custom Entra app registration, Claude Desktop and Codex must use the local server. Local server: interactive Microsoft sign-in, Azure CLI, credential chain, bearer token or PAT. · Maintenance: Remote server https://mcp.dev.azure.com/{organization} (preview, recommended by Microsoft); local server release v2.11.0 on 2026-10-22 (npm @azure-devops/mcp 2.11.0); last commit 2026-10-22
- Buildkite MCP Server
- Connect your client to Buildkite's hosted remote MCP server (OAuth), or run the local `buildkite-mcp-server stdio` with BUILDKITE_API_TOKEN (see the official docs). official docs ↗Credentials: Buildkite OAuth on the hosted remote server, or a Buildkite API access token (BUILDKITE_API_TOKEN) for the local server. · Maintenance: Release v1.29.0 on 2026-10-20; last commit 2026-10-23
- CircleCI MCP Server (hosted)
- Connect to https://mcp.circleci.com/v1/mcp (Streamable HTTP, OAuth2). Claude Code: `claude mcp add --transport http circleci-mcp-server https://mcp.circleci.com/v1/mcp`, then /mcp > Authenticate; Claude and Cursor: add CircleCI from their directories; VS Code: type http. official docs ↗Credentials: CircleCI account via OAuth2 from the client; hosts that cannot do OAuth use a CircleCI personal API token. · Maintenance: Hosted remote server; setup docs last updated 2026-09-28. Replaces the deprecated local @circleci/mcp-server-circleci (npm 0.20.0, repo to be archived). The CircleCI CLI (v1.11.0, 2026-10-21) can also expose its commands as a local MCP server (`circleci mcp`).
Set up any of these in your client: Claude Code · Cursor · VS Code · Claude Desktop. Filter interactively on the CI/CD explorer, or ask the catalog from your agent with the free MCP server.
Other comparisons: Databases & SQL · Git & GitHub repos · Code review · Infra & deploy · Debugging & observability · Library docs & research · Web fetching & scraping · Frontend & UI · Local files · Docs & writing · Build AI apps · Planning & reasoning · Utilities
⚠ No independent security audit: entries summarize official sources only. Review permissions and code before installing.