# ofershap/mcp-server-github-actions [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/ofershap/mcp-server-github-actions  
**GitHub Stars:** 4  
**npm Downloads (last month):** 247  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ofershap-mcp-server-github-actions

## Description
GitHub Actions — view workflow runs, read logs, re-run failed jobs, and manage CI/CD.

## Tools
Capabilities this server exposes over MCP:

- **list_workflows** — List all workflow files in a GitHub repository.
- **list_runs** — List workflow runs for a repository. Optionally filter by workflow or status.
- **get_run** — Get details of a specific workflow run.
- **get_run_logs** — Get logs URL for a workflow run. GitHub returns a redirect to a zip file.
- **rerun_workflow** — Re-run a complete workflow run.
- **rerun_failed_jobs** — Re-run only the failed jobs from a workflow run.
- **cancel_run** — Cancel a workflow run that is in progress or queued.
- **list_artifacts** — List artifacts produced by a workflow run.
- **trigger_workflow** — Trigger a workflow run via workflow_dispatch. Requires a workflow with workflow_dispatch enabled.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-github-actions": {
    "command": "npx",
    "args": ["-y","mcp-server-github-actions"],
    "env": {
      "GITHUB_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `GITHUB_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What ofershap/mcp-server-github-actions MCP server does

The ofershap/mcp-server-github-actions MCP server exposes GitHub Actions operations as tools for an AI assistant. It works with repositories and workflow runs through GitHub's REST API, covering both read and write actions.

Read operations include listing workflow files, finding runs, filtering runs by workflow or status, retrieving details for a specific run, obtaining the logs URL, and listing artifacts. The logs tool returns the URL GitHub provides; GitHub redirects that URL to a ZIP archive rather than returning parsed log text directly.

Write operations include rerunning an entire workflow run, rerunning only failed jobs, canceling a queued or in-progress run, and starting a workflow with `workflow_dispatch`. The target workflow must have `workflow_dispatch` enabled before it can be triggered.

## How it works

The ofershap/mcp-server-github-actions MCP server runs as a command-line MCP process and can be started with `npx mcp-server-github-actions`. An MCP-compatible client launches the process and passes requests to its tools. The server then uses the supplied GitHub token to call the relevant GitHub Actions endpoints.

Typical requests can identify a repository, workflow, branch, or run ID. For example, an agent can locate recent runs, inspect a selected run, retrieve its log archive URL, and rerun failed jobs without requiring a separate browser session. The available operations are limited to the GitHub Actions functionality exposed by the listed tools; repository, issue, and pull-request management is not described as part of this server.

## Setup and configuration

Install or run the package through `npx` and configure it as a standard MCP server. The required environment variable is `GITHUB_TOKEN`. Set that variable in the MCP client's server configuration rather than embedding the credential in an installation link.

The README provides configurations for Cursor, Claude Desktop, and VS Code. Each uses the `npx` command with the package name and passes the token through the server's environment block. The repository also includes an Agent Plugins package. For Cursor, the plugin can be cloned and copied or symlinked into `~/.cursor/plugins/local/mcp-server-github-actions`, then the window can be reloaded; the token still needs to be configured separately.

Create a GitHub personal access token with access to the repositories the agent will manage. Fine-grained tokens should enable Actions read and write permissions for the selected repositories. A classic token can use the `repo` scope.

## Tools and capabilities

The server provides these tools:

- `list_workflows`: lists workflow files in a repository.
- `list_runs`: lists workflow runs, with optional workflow and status filters.
- `get_run`: returns details for a specified run.
- `get_run_logs`: returns GitHub's log URL for a run.
- `rerun_workflow`: reruns a complete workflow run.
- `rerun_failed_jobs`: reruns only failed jobs.
- `cancel_run`: cancels a queued or in-progress run.
- `list_artifacts`: lists artifacts from a workflow run.
- `trigger_workflow`: starts a workflow through `workflow_dispatch`.

The ofershap/mcp-server-github-actions MCP server is suited to checking CI status, investigating failed runs, repeating selected jobs, stopping builds, reviewing produced artifacts, and initiating workflows that are configured for manual dispatch.

## Limitations and notes

A GitHub token with suitable Actions permissions is required. Triggering a workflow requires `workflow_dispatch` to be enabled in that workflow. The log-reading tool provides a download URL that redirects to a ZIP file, so clients or agents may need to handle that archive separately.

The README names Claude Desktop, Cursor, and VS Code Copilot as supported clients and states that the package works with any MCP client. There is no one-click Cursor or VS Code installation because the token must remain in the environment configuration.

_Full upstream README: https://allmcps.com/mcp/ofershap-mcp-server-github-actions/readme_