Server facts
mcp-server-github-actions
Project
- Author
- ofershap
- License
- MIT
- Category
- Version Control
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 4
- Last commit
- Data as of
Overview
GitHub Actions troubleshooting starts with finding the relevant workflow and run. mcp-server-github-actions exposes tools for listing repository workflows, filtering runs by workflow or status, and retrieving details about an individual run. Developers can use these through an AI assistant to investigate CI activity while working in their editor. For log access, the server returns a download URL pointing to a ZIP archive rather than supplying parsed log contents. A separate tool lists the artifacts associated with a run.
The control tools distinguish between retrying a whole run and retrying just its failed jobs. They also support cancellation for queued or active runs. Starting a workflow uses workflow_dispatch, so the target workflow must have that event enabled. The server communicates over stdio and runs on Node.js, with documented use in Cursor, Claude Desktop, and VS Code Copilot. Access depends on a GitHub token carrying Actions permissions; the README describes both fine-grained tokens with Actions read/write access and classic tokens using the repo scope.
mcp-server-github-actions setup notes
- mcp-server-github-actions records stdio only; confirm a network transport upstream before planning remote access.