Log inSubmit server
MCP Server Github Actions logo

MCP Server Github Actions

by ofershap

Manage GitHub Actions workflows, inspect runs and logs, rerun jobs, cancel builds, list artifacts, and trigger deployments through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server Github Actions

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ofershap-mcp-server-github-actions": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-github-actions"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

The ofershap/mcp-server-github-actions MCP server connects an MCP client to GitHub Actions through the GitHub REST API. It lets agents inspect workflows and runs, retrieve log download URLs, rerun workflows or failed jobs, cancel queued or active runs, list artifacts, and dispatch workflows. Run it with npx and provide a GitHub token with Actions permissions. Reach for it when CI/CD investigation or workflow control would otherwise require switching to GitHub's web interface.

Use cases

  • List recent workflow runs for a repository
  • Inspect a failed CI run and retrieve its log archive URL
  • Rerun only failed jobs from a workflow run
  • Cancel a queued or in-progress build
  • Trigger a manually dispatchable deployment workflow

Key features

  • List workflows and workflow runs
  • Filter runs by workflow or status
  • Retrieve run details and log URLs
  • Rerun complete workflows or failed jobs
  • Cancel runs and list artifacts
  • Trigger workflow_dispatch workflows

Tools9

What MCP Server Github Actions lets your agent do. Expand a tool for its parameters.

Verified live~1.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

17/18 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · mcp-server-github-actions (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads247Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Tools exposed9Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Github Actions works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server Github Actions

ofershap/mcp-server-github-actions is an MCP server that connects AI assistants to GitHub Actions through the GitHub REST API. Its main tools list workflows and runs, retrieve run details and log URLs, rerun workflows or failed jobs, cancel runs, list artifacts, and trigger workflows configured with workflow_dispatch.

Run it with npx mcp-server-github-actions and add that command to your MCP client configuration. Set GITHUB_TOKEN in the server's environment block. The README includes JSON examples for Cursor, Claude Desktop, and VS Code.

It needs a GitHub personal access token with Actions read and write permission for the repositories it manages. Fine-grained tokens should enable Actions access for selected repositories; classic tokens can use the repo scope.

Yes, it works with Cursor through the standard MCP configuration. Add the npx command and GITHUB_TOKEN to Cursor's MCP settings, or use the repository's Agent Plugin setup with a local plugin directory.

No, triggering requires the target workflow to have workflow_dispatch enabled. The trigger_workflow tool starts a workflow through that dispatch mechanism; workflows without it cannot be started with this tool.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server Github Actions AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ofershap-mcp-server-github-actions?style=directory)](https://allmcps.com/mcp/ofershap-mcp-server-github-actions)
HTML Embed
<a href="https://allmcps.com/mcp/ofershap-mcp-server-github-actions"><img src="https://allmcps.com/api/badge/ofershap-mcp-server-github-actions?style=directory" alt="MCP Server Github Actions on AllMCPs" /></a>