ofershap/mcp-server-github-actions · Archived

github-actions-management

Manage GitHub Actions workflows via MCP. Use when CI failed, the user asks why a workflow run failed, to re-run failed jobs, cancel a queued run, list workflow artifacts, trigger workflow_dispatch, or check deployment status for owner/repo.

First seen Mar 5, 2026

Installation

$ npx skills add ofershap/mcp-server-github-actions --skill github-actions-management

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,663 B
  • docs SUMMARY.md 273 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

GitHub Actions Management via MCP

Use this skill when you need to check CI/CD status, read workflow logs, re-run failed jobs, or trigger deployments.

Available Tools

Tool What it does
list_workflows List all workflow files in a repository
list_runs List workflow runs (filter by workflow or status)
get_run Get details of a specific workflow run
getrunlogs Get the logs URL for a run (zip download)
rerun_workflow Re-run an entire workflow run
rerunfailedjobs 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

Workflow

  1. Use list_runs with owner and repo to see recent runs and their status
  2. For failed runs: getrun for details, then decide whether to rerunfailed_jobs or investigate logs
  3. triggerworkflow requires the workflow file name and a branch — the workflow must have a workflowdispatch trigger

Key Patterns

  • All tools require owner and repo parameters (e.g., owner: "ofershap", repo: "my-project")
  • listruns supports status filter: "completed", "inprogress", "queued", "failure", "success"
  • rerunfailedjobs is preferred over rerun_workflow; it is faster and cheaper
  • triggerworkflow needs workflowid (filename like "ci.yml") and ref (branch name)

Error Scenarios

  • 401/403 from GitHub: GITHUB_TOKEN missing, expired, or lacks Actions scope on the repo
  • Run or workflow not found: double-check owner, repo, and numeric run id from list_runs
  • triggerworkflow rejected: workflow file lacks workflowdispatch or branch ref is wrong
  • getrunlogs returns a zip URL only: download and unzip outside the tool to read full log text

Safety

  • Prefer rerunfailedjobs over full rerun_workflow to avoid unnecessary compute
  • Confirm before cancel_run; the user may want the run to finish
  • trigger_workflow can trigger deployments; always confirm the target branch