list_workflowsLABSCO SUMMARY
From a red run to a re-run, without the browser.
The loop it shortens is the one behind a red CI badge: list the recent runs, open the failed one to see which job broke, then re-run it or cancel a stuck run. It reads run and job status, not log output. The repository is archived, and its README points to Actions support in the official GitHub MCP server instead.
What it is
An MCP server over the GitHub Actions API: list a repository's workflows, walk their runs, open the jobs inside one, read usage statistics, and trigger, cancel or re-run a workflow.
What you get
- Workflows listed for a repository, and one workflow's details read by ID or filename (list_workflows, get_workflow)
- Runs listed for the repository or for a single workflow, with pagination (list_workflow_runs)
- One run opened, and the jobs inside it (get_workflow_run, get_workflow_run_jobs)
- Usage statistics for a workflow, including billable minutes (get_workflow_usage)
- A workflow started on a branch, tag or commit with its inputs, and a run cancelled or re-run (trigger_workflow, cancel_workflow_run, rerun_workflow)
- Timeout handling, rate limiting and strict URL validation on the API calls
Requirements
A GitHub token with access to the repository you are asking about, handed to the server in its environment.
Setup effort
Build from source — git clone https://github.com/ko1ynnky/github-actions-mcp-server.git
USE CASES
01
Re-running a build that failed
Find the failed run among the recent ones, then re-run it — or cancel a run that is stuck.
02
Seeing which job in a run failed
Open the run, then the jobs inside it.
03
Telling a new failure from a recurring one
List recent runs for that workflow and compare.
04
Getting oriented in a repository's automation
List the workflows, then read the one that matters.
05
Seeing where Actions minutes are going
Read the usage statistics per workflow.
9 tools
Listed in project docs. Your client may show a different list.
get_workflowget_workflow_usagelist_workflow_runsget_workflow_runget_workflow_run_jobstrigger_workflowcancel_workflow_runrerun_workflowBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- Node.js
- npm
- GITHUB_PERSONAL_ACCESS_TOKEN in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/ko1ynnky/github-actions-mcp-server.git
cd github-actions-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop, Codeium, Windsurf
JSON
{
"mcpServers": {
"github-actions": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SERVER>/dist/index.js"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
