Github Actions

io.github.ofershapPublished by GitHub account ofershapv1.0.1Updated Oct 24, 2026

GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD.

The publisher's own server: actions.world

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant inspect and control GitHub Actions CI/CD: list workflows and runs, read logs, re-run jobs, cancel builds, and trigger workflows.

What you can do
Wraps the GitHub REST API for Actions workflows. Tools include list_workflows, list_runs, get_run, get_run_logs (returns a logs zip download URL), rerun_workflow, rerun_failed_jobs, cancel_run, list_artifacts, and trigger_workflow via workflow_dispatch. It focuses on workflow runs rather than repos, issues, or pull requests.
When to use it
Useful when CI fails and you want to ask why the last run failed, re-run failed jobs, cancel a stuck build, list artifacts, or trigger a deployment workflow without leaving the editor.
Requirements
Runs locally over stdio, typically via npx mcp-server-github-actions, so Node.js is needed. Requires a GitHub personal access token supplied as the GITHUB_TOKEN environment variable, with Actions read and write permission on the target repositories. Network access to the GitHub API is required.
Before you install
The GITHUB_TOKEN is a credential granting write access to Actions on the selected repositories; keep it out of shared configs and use fine-grained tokens scoped to specific repos. Tools can change state: rerun_workflow, rerun_failed_jobs, cancel_run, and trigger_workflow start, stop, or dispatch CI runs, and trigger_workflow may deploy. Logs and run data are fetched from GitHub.

Installation

In SourceWeft

  1. Open Github Actions in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-server-github-actions

[npm version] [npm downloads] [CI] [TypeScript] [License: MIT] [Agent Plugins]

Manage GitHub Actions workflows from your AI assistant. List runs, read logs, re-run failed jobs, cancel builds, and trigger deployments without leaving your editor.

bash
npx mcp-server-github-actions

Works with Claude Desktop, Cursor, VS Code Copilot, and any MCP client. Requires a GitHub token with Actions permissions.

[MCP server for GitHub Actions workflows, CI/CD runs, and deployment logs]

Demo built with remotion-readme-kit

Why

GitHub's official MCP server covers repos, issues, and PRs, but it doesn't touch Actions. That means when your CI fails, you still have to open a browser, find the run, click through to the logs, and figure out what went wrong. This server fills that gap. You can ask your assistant "why did the last CI run fail?" or "re-run the failed jobs" and get answers right where you're working. It uses the same GitHub REST API you'd use manually, just without the context switching.

Tools

ToolDescription
list_workflowsList all workflow files in a repository
list_runsList workflow runs (optionally filter by workflow or status)
get_runGet details of a specific workflow run
get_run_logsGet the logs URL for a run (zip file download)
rerun_workflowRe-run an entire workflow run
rerun_failed_jobsRe-run only the failed jobs from a run
cancel_runCancel an in-progress or queued run
list_artifactsList artifacts produced by a workflow run
trigger_workflowTrigger a workflow via workflow_dispatch

Quick Start

Cursor

Add to your Cursor MCP settings (e.g. ~/.cursor/mcp.json or project-level):

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

Claude Desktop

Add to claude_desktop_config.json:

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

VS Code

Add to user settings or .vscode/mcp.json:

json
{  "mcp": {    "servers": {      "github-actions": {        "command": "npx",        "args": ["-y", "mcp-server-github-actions"],        "env": {          "GITHUB_TOKEN": "<your-token>"        }      }    }  }}

Auth

Create a GitHub Personal Access Token:

  1. Settings > Developer settings > Personal access tokens
  2. Choose Fine-grained tokens (recommended) or Tokens (classic)
  3. Fine-grained: select your repos, then enable Actions: Read and Write
  4. Classic: enable the repo scope (includes Actions)

Agent Plugins

This repo is an Agent Plugins 1.0.0 package: plugin.json, portable mcp.json, and skills/ ship together with the MCP server.

For Cursor, clone the repo and copy or symlink it to ~/.cursor/plugins/local/mcp-server-github-actions, then reload the window. Skills and MCP show up under Customize > Plugins.

Agent Plugins v1 does not ship OAuth. Set GITHUB_TOKEN in your MCP client config (see Quick Start). One-click Cursor/VS Code install is not offered because the token must stay in env.

FAQ

What is mcp-server-github-actions?

An MCP server for GitHub Actions: list runs, fetch run details, re-run failed jobs, cancel runs, list artifacts, and trigger workflow_dispatch.

What token do I need?

A GitHub PAT with Actions read/write on the repos you manage. Set GITHUB_TOKEN in the MCP server env block.

How is this different from the official GitHub MCP?

The official server covers repos, issues, and PRs. This one focuses on workflow runs, logs URLs, reruns, and dispatch triggers.

Can I install it as an Agent Plugin in Cursor?

Yes, via ~/.cursor/plugins/local/mcp-server-github-actions. You still configure GITHUB_TOKEN in Cursor MCP settings.

Why is there no one-click install button?

The token cannot be embedded safely in a portable install link. Use the JSON snippet under Quick Start.

Example Prompts

  • "List the last 5 workflow runs for ofershap/mcp-server-docker"
  • "Show me the workflows in the microsoft/vscode repo"
  • "Get details for run 12345 in owner/repo"
  • "Re-run the failed jobs for run 67890 in my-org/my-repo"
  • "Cancel the currently running workflow run 11111"
  • "List artifacts from the latest run in owner/repo"
  • "Trigger the deploy.yml workflow on the staging branch for my-org/my-app"
  • "What's the status of the most recent CI run for this project?"

Development

bash
npm installnpm run typechecknpm run buildnpm testnpm run lintnpm run format

See also

More MCP servers and developer tools on my portfolio.

Author

[Made by ofershap]

[LinkedIn] [GitHub]


README built with README Builder

License

MIT © 2026 Ofer Shapira

Source: README.md at commit 1ac8489

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Actions integrations