GitHub Actions MCP Server
Related Servers
Alternatives to GitHub Actions MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that diagnoses GitHub Actions workflow failures and automatically creates repair pull requests using LLM-generated unified diffs. It includes a governance layer to orchestrate autonomous fixes or human-reviewed repairs based on risk assessment thresholds.-
- FlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to perform GitHub operations like creating repositories, issues, and commits through natural language.-
- FlicenseAqualityCmaintenanceMCP server that lets AI agents interact with GitHub using natural language, supporting operations like creating repositories, issues, and commits.5-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.MIT
- AlicenseAqualityAmaintenanceAn MCP server that gives AI agents full visibility and control over your Dagster instance, enabling autonomous monitoring, diagnosis, and remediation of data pipelines.1714MIT
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables developers to summon AI development team agents directly from their IDE to help with tasks like PR reviews, security evaluation, and CI/CD deployment setup.-
TDQS
Scored across 13 tools
Each tool targets a distinct resource or action within GitHub Actions: repositories, workflows, workflow runs, logs, failure analysis, reruns, cancellations, artifacts, deployments, rollback, and monitoring. Even the closely related watch and get run tools are clearly separated by their blocking versus snapshot behavior.
All tools follow the github_verb_noun pattern with snake_case, but there are minor deviations: github_watch_workflow actually watches a run, and github_analyze_failure omits the specific object. These are small inconsistencies in an otherwise predictable naming scheme.
13 tools is well-scoped for a GitHub Actions MCP server, covering the essential operational workflows without unnecessary bloat. The count fits comfortably within the ideal 3-15 range and each tool serves a clear purpose.
The tool set covers the core run lifecycle (list, get, logs, rerun, cancel, watch), plus artifacts and deployment rollback. However, it lacks the ability to manually trigger a workflow run (workflow_dispatch), which is a notable gap for a GitHub Actions server, though not a fatal one.