Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"github-actions": {
"env": {
"GITHUB_TOKEN": "<your-token>"
},
"args": [
"-y",
"mcp-server-github-actions"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-server-github-actions' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-server-github-actions against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools / devops
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for io.github.ofershap/github-actions and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
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.
| 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 |
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>"
}
}
}
}
Add to claude_desktop_config.json:
{
"mcpServers": {
"github-actions": {
"command": "npx",
"args": ["-y", "mcp-server-github-actions"],
"env": {
"GITHUB_TOKEN": "<your-token>"
}
}
}
}
Configure your MCP client to run:
npx mcp-server-github-actions
Make sure GITHUB_TOKEN is set in the environment (e.g. in your shell profile or client config).
Create a GitHub Personal Access Token:
repo scope (includes Actions)