GitHub Actions MCP server
✓ VerifiedManage GitHub Actions workflows by listing runs, reading logs, re-running failed jobs, and triggering deployments directly from an AI assistant.
Also known as ofershap/mcp-server-github-actions, mcp-server-github-actions
- Stars
- 5
- Tools
- 9
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Aug 10, 2026
- License
- MIT
What is GitHub Actions MCP?
GitHub Actions manages GitHub Actions workflows by listing runs, reading logs, re-running failed jobs, and triggering deployments directly from an AI assistant. It exposes 9 tools, such as list_workflows, list_runs, get_run.
Summary generated from the project's README
About GitHub Actions MCP server
Managing CI/CD pipelines directly from your coding environment is what this server enables for developers using Claude Desktop, Cursor, or VS Code Copilot. While official GitHub MCP implementations focus on issues and pull requests, this tool specifically targets GitHub Actions workflows. It allows you to monitor builds, inspect logs, and manage the lifecycle of your automation without switching to a web browser.
Users connect the server by providing a GitHub Personal Access Token with Actions read and write permissions via an environment variable. Once configured, you can use tools like list_runs to check status, get_run_logs to access log files, and rerun_failed_jobs to fix broken builds. The server also supports more advanced operations such as canceling active runs, listing workflow artifacts, and using trigger_workflow to initiate deployments via workflow_dispatch.
What you can do with it
- 1Debug failing CI buildsAsk your assistant to explain why the most recent continuous integration run failed by inspecting the logs.
- 2Recover from interrupted workflowsInstruct the AI to restart only the specific jobs that did not complete successfully in a previous run.
- 3Execute manual deploymentsTrigger a specific deployment workflow on a designated branch using a natural language command.
- 4Monitor workflow activityRetrieve a list of all available workflow files or recent execution history for a repository.
Written from the project's README. Every use case is checked against a quote from it.
How to install GitHub Actions MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall GitHub Actions MCP in Claude Code
$ claude mcp add mcp-server-github-actions -- npx -y mcp-server-github-actionsInstall GitHub Actions MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server-github-actions": {
"command": "npx",
"args": [
"-y",
"mcp-server-github-actions"
]
}
}
}Install GitHub Actions MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server-github-actions": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-github-actions"
]
}
}
}Install GitHub Actions MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server-github-actions","type":"stdio","command":"npx","args":["-y","mcp-server-github-actions"]}'Install GitHub Actions MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server-github-actions": {
"command": "npx",
"args": [
"-y",
"mcp-server-github-actions"
]
}
}
}Install GitHub Actions MCP in Codex
$ codex mcp add mcp-server-github-actions -- npx -y mcp-server-github-actionsInstall GitHub Actions MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server-github-actions] command = "npx" args = ["-y", "mcp-server-github-actions"]
Install GitHub Actions MCP in Gemini CLI
$ gemini mcp add -s user mcp-server-github-actions npx -- -y mcp-server-github-actionsInstall GitHub Actions MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server-github-actions": {
"command": "npx",
"args": [
"-y",
"mcp-server-github-actions"
]
}
}
}GitHub Actions MCP tools 9
Detected from the READMElist_workflowslist_runsget_runget_run_logsrerun_workflowrerun_failed_jobscancel_runlist_artifactstrigger_workflow
| list_workflows | — | |
| list_runs | — | |
| get_run | — | |
| get_run_logs | — | |
| rerun_workflow | — | |
| rerun_failed_jobs | — | |
| cancel_run | — | |
| list_artifacts | — | |
| trigger_workflow | — |
Configuration
GITHUB_TOKEN
| Name | Description | |
|---|---|---|
| GITHUB_TOKEN | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableofershap/mcp-server-github-actions is public and reachablegithub.com/ofershap/mcp-server-github-actions ↗Pass
- Package names this repository as its sourcemcp-server-github-actions names ofershap/mcp-server-github-actions as sourcenpmjs.com/package/mcp-server-github-actions ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-10github.com/ofershap/mcp-server-github-actions ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from mcp-server-github-actionsPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model9 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubmcp-server-github-actions
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.
npx mcp-server-github-actions
Works with Claude Desktop, Cursor, VS Code Copilot, and any MCP client. Requires a GitHub token with Actions permissions.

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
| Tool | Description |
|---|---|
list_workflows |
List all workflow files in a repository |
list_runs |
List workflow runs (optionally filter by workflow or status) |
get_run |
Get details of a specific workflow run |
get_run_logs |
Get the logs URL for a run (zip file download) |
rerun_workflow |
Re-run an entire workflow run |
rerun_failed_jobs |
Re-run only the failed jobs from a run |
cancel_run |
Cancel an in-progress or queued run |
list_artifacts |
List artifacts produced by a workflow run |
trigger_workflow |
Trigger a workflow via workflow_dispatch |
Quick Start
Cursor
Add to your Cursor MCP settings (e.g. ~/.cursor/mcp.json or project-level):
{
"mcpServers": {
"github-actions": {
"command": "npx",
"args": ["-y", "mcp-server-github-actions"],
"env": {
"GITHUB_TOKEN": "<your-token>"
}
}
}
}
Claude Desktop
Add to claude_desktop_config.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:
{
"mcp": {
"servers": {
"github-actions": {
"command": "npx",
"args": ["-y", "mcp-server-github-actions"],
"env": {
"GITHUB_TOKEN": "<your-token>"
}
}
}
}
}
Auth
Create a GitHub Personal Access Token:
- Settings > Developer settings > Personal access tokens
- Choose Fine-grained tokens (recommended) or Tokens (classic)
- Fine-grained: select your repos, then enable Actions: Read and Write
- Classic: enable the
reposcope (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
npm install
npm run typecheck
npm run build
npm test
npm run lint
npm run format
See also
More MCP servers and developer tools on my portfolio.
Author
README built with README Builder
License
MIT © 2026 Ofer Shapira
GitHub Actions MCP questions
How do I add GitHub Actions MCP to Claude Code?
Run claude mcp add mcp-server-github-actions -- npx -y mcp-server-github-actions in your terminal. Add --scope user to make it available in every project.
How do I add GitHub Actions MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does GitHub Actions MCP provide?
It exposes 9 tools, including list_workflows, list_runs, get_run, get_run_logs, rerun_workflow.
What is mcp-server-github-actions?
It is an MCP server that allows you to list runs, fetch run details, re-run failed jobs, cancel runs, list artifacts, and trigger workflow_dispatch.
What token do I need to use this server?
You need a GitHub Personal Access Token (PAT) with Actions read and write permissions for the repositories you manage.
How does this differ from the official GitHub MCP server?
While the official server handles repositories, issues, and pull requests, this server specifically focuses on workflow runs, logs, reruns, and dispatch triggers.
Can I install this as an Agent Plugin in Cursor?
Yes, you can install it via ~/.cursor/plugins/local/mcp-server-github-actions and must still configure your GITHUB_TOKEN in the Cursor MCP settings.