Summary
Straight to the failing run's logs.
get_latest_failed_run_logs is the reason to install it: the usual route to a red CI badge is several clicks, and here it is one call. Read the repository notice first, though, because the maintainer plans to archive it once the official GitHub MCP server ships Actions support.
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 pull the logs from the most recent failure.
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)
- The logs from the most recent failed run, fetched in one call (get_latest_failed_run_logs)
- 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
One command plus a key — npx -y github-actions-mcp, then supply credentials