GitHub Actions MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log verbosity: debug / info / warn / error | info |
| GITHUB_TOKEN | Yes | GitHub Personal Access Token with scopes repo, workflow, read:org | |
| ANTHROPIC_API_KEY | Yes | Anthropic API key for Claude-powered failure analysis | |
| POLLING_INTERVAL_MS | No | How often monitor_repository polls GitHub (milliseconds) | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_list_repositoriesA | List GitHub repositories accessible with the current token. Returns name, description, language, stars, visibility, and last update time. |
| github_list_workflowsA | List all GitHub Actions workflows defined in a repository. |
| github_list_workflow_runsA | List recent runs of a GitHub Actions workflow, with optional filters for status and branch. |
| github_get_workflow_runA | Get detailed information about a specific workflow run, including its jobs and their statuses. |
| github_watch_workflowA | Watch a workflow run until it completes (or times out after 5 minutes). Polls every 10 seconds and returns the final status and conclusion. |
| github_get_workflow_logsA | Retrieve and parse the execution logs for a specific workflow run. Returns structured per-job logs with error extraction. |
| github_analyze_failureA | Automatically analyze a failed GitHub Actions workflow run using AI. Returns the probable cause, suggested fixes, severity, and a diagnostic report. |
| github_rerun_workflowA | Rerun a GitHub Actions workflow. Use mode 'all' to rerun the entire workflow, or 'failed' to rerun only the failed jobs. |
| github_cancel_workflowA | Cancel a workflow run that is currently queued or in progress. |
| github_download_artifactsA | List and get download URLs for artifacts produced by a workflow run. Returns artifact names, sizes, and pre-signed download URLs. |
| github_get_deploymentsA | List deployments for a repository, optionally filtered by environment. Returns deployment ID, environment, status, ref, and creator. |
| github_rollback_deploymentA | Roll back to a previous deployment by creating a new deployment pointing to a specific ref and marking the current deployment as inactive. |
| github_monitor_repositoryB | Start or stop continuous monitoring of a repository's GitHub Actions. Returns the list of currently monitored repositories. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.