Developer toolsPublic source

CI/CD MCP Server

Give your AI agents visibility into CI/CD pipelines. This MCP server connects to GitHub Actions so agents can check build status, read logs, download artifacts, trigger deployments, and re-run failed jobs — all through…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides cicd capabilities through a typed MCP contract.

Architecture

How CI/CD MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

CI/CD MCP Server

Validates the request and owns 8 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

CI/CD MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask CI/CD MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

8 named tools

list_pipeline_runs

List CI/CD pipeline runs (GitHub Actions workflows)

read only

get_pipeline_run

Get details of a specific pipeline run including jobs and timing

read only

get_pipeline_logs

Get logs for a pipeline run or specific job

read only

rerun_pipeline

Re-run a failed pipeline run

external write

list_artifacts

List or download artifacts from a pipeline run

read only

get_deployment_status

Get deployment status for an environment

read only

trigger_deployment

Trigger a deployment workflow for an environment

external write

cancel_pipeline

Cancel a running pipeline

external write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

5 read only3 external write

The registry manifest declares read only, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-cicd

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-cicd",
    ["mcp-cicd"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring