CD MCP Server

What GitHub CI/CD MCP Server MCP server does

GitHub CI/CD MCP Server provides MCP tools for GitHub repository and delivery workflows. It connects to GitHub REST and GraphQL APIs and also exposes commands that operate on a local git checkout. The tool set covers both read and write actions, so the permissions assigned to the token determine which operations are available.

Repository tools can create, inspect, list, fork, and branch repositories. Other groups handle commits, comparisons, combined status, check runs, pull requests, reviews, issues, comments, releases, tags, branch protection, webhooks, collaborators, and teams. CI/CD-specific tools inspect workflows, runs, jobs, artifacts, deployments, and environments. GraphQL query, mutation, and repository overview tools supplement the REST operations.

How it works

The server runs as an MCP process and communicates with clients over the configured command. The recommended setup uses npx to download and execute the published @kinus/github-cicd-mcp package. A client sends tool calls through MCP; the server then uses the configured GitHub credentials to call REST or GraphQL endpoints, or executes the requested local git operation.

GitHub Actions tools can list workflows and runs, inspect jobs, rerun or cancel runs, dispatch workflows, list Actions secrets and variables, and retrieve workflow artifacts. Deployment tools can list deployments, create deployments and statuses, and list environments. Local tools include status, commit, push, pull, log, and clone operations.

Setup and configuration

For the npm installation, add a server entry whose command is npx, with -y and @kinus/github-cicd-mcp as arguments. Pass the GitHub token through the GITHUB_TOKEN environment variable, or use GH_TOKEN in the system environment. Tokens should remain in environment variables and should not be committed to a repository.

A source installation requires cloning the repository, running npm install, building with npm run build, and pointing MCP to the resulting dist/index.js file. Development verification is available through npm run verify.

GitHub CI/CD MCP Server can target GitHub Enterprise by setting GITHUB_HOST, GITHUB_API_URL, and GITHUB_GRAPHQL_URL. The token permissions depend on the operation: repository work may require repo or fine-grained Contents, pull request, and Issues permissions; Actions uses workflow; organization billing requires read:org and an appropriate billing role; and administrative operations require repository or organization admin access.

Tools and capabilities

The documented tool groups include:

• Repository, branch, commit, status, pull request, issue, release, and tag management.
• Workflow, run, job, artifact, Actions secret, and Actions variable inspection.
• Workflow dispatch, rerun, and cancellation operations.
• Deployment creation and status reporting.
• User and organization Actions billing information and usage reports.
• Webhook, collaborator, team, and branch protection operations.
• Arbitrary GraphQL queries and mutations, plus a repository overview helper.
• Local git status, history, synchronization, cloning, committing, and pushing.

Limitations and notes

Operations are constrained by the GitHub token’s scopes, fine-grained permissions, and administrative roles. Organization billing and administrative tools need additional access beyond ordinary repository permissions. The README identifies Cursor and Claude Desktop as target MCP clients, but does not document behavior for particular tool calls beyond the listed capabilities. Review the project’s security guidance before deploying credentials or enabling write and administrative operations.