Creativity · MCP — server

MCP GitHub Actions Server

GitHub Actions is the default CI/CD for most new repositories on GitHub. While the general GitHub MCP covers much of it, a dedicated MCP GitHub Actions server focuses specifically on workflow runs, job logs, artifacts, and reruns — letting Claude drill into CI failures fast.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio

Capabilities

Tools: list_workflow_runs, get_workflow_run, get_job_logs, download_artifact, rerun_failed_jobs, cancel_workflow_run
Fine-grained PAT or GitHub App token
Rate-limit aware

Install

npx -y @modelcontextprotocol-community/server-github-actions

Configuration

{
  "mcpServers": {
    "github-actions": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol-community/server-github-actions"],
      "env": {
        "GITHUB_TOKEN": "<fine-grained-pat>"
      }
    }
  }
}

Frequently asked questions

Why a dedicated Actions server instead of the general GitHub one?

Tighter focus and clearer tool surface. If all you care about is CI triage, a workflow-focused server keeps tool usage cleaner and prompts smaller.

Can I use it in GitHub Enterprise Server?

Yes — set GITHUB_API_URL to your enterprise API base, and the server routes correctly.

What about the `actions/*` REST endpoints?

The server maps to those endpoints directly; self-hosted runner management and workflow dispatching are supported.

Sources

GitHub Actions REST API — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20