mcp-server-github-actions
Related Servers
Alternatives to mcp-server-github-actions
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that analyzes GitHub Actions workflow performance, audits configuration for optimization, and provides billing and cache usage insights.316 npm2MIT
- AlicenseCqualityFmaintenanceAn MCP server that enables AI assistants to manage GitHub Actions workflows by providing tools for listing, viewing, triggering, canceling, and rerunning workflows through the GitHub API.918 npm41MIT
- AlicenseAqualityDmaintenanceAn intelligent MCP server that gives AI agents full control over GitHub Actions CI/CD pipelines, including real-time monitoring, log analysis, AI-powered failure diagnosis, and deployment management.13256 npm1ISC
- AlicenseNot gradedqualityCmaintenanceMCP server that pushes GitHub Actions CI/CD results and PR events into Claude Code sessions, enabling automatic investigation and remediation.7 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for GitHub Actions CI failure triage. It wraps the gh CLI to fetch PR checks, failed jobs, and tail/grep failed job logs with ANSI/timestamp stripping and root-cause extraction.5MIT
- FlicenseNot gradedqualityBmaintenanceHTTP MCP server for GitHub API with tools for file manipulation, commit listing, and workflow logs.-
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific GitHub Actions operations: canceling runs, getting run details, retrieving logs, listing artifacts, listing runs, listing workflows, rerunning failed jobs, rerunning entire workflows, and triggering workflows. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun naming pattern (e.g., cancel_run, get_run, list_artifacts) with clear, descriptive names. The pattern is maintained throughout the set without any deviations or mixed conventions.
With 9 tools, the server is well-scoped for managing GitHub Actions workflows, covering key operations like monitoring, triggering, and managing runs. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete coverage for GitHub Actions management, including listing workflows and runs, triggering and rerunning workflows, canceling runs, accessing logs and artifacts, and handling failed jobs. There are no obvious gaps in the lifecycle or workflow operations.