GitHub Actions MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token (classic or fine-grained) with required scopes: repo (for private repos), actions:read (minimum for read-only), actions:write (for trigger/cancel) | |
| GHA_MCP_FALLBACK_KEY | No | Optional Anthropic API key for fallback AI (Haiku) integration for log analysis |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gha_list_workflowsB | List workflows in a repository |
| gha_get_workflowC | Get workflow definition and metadata |
| gha_list_runsC | List workflow runs with filtering |
| gha_get_runC | Get detailed run information including jobs |
| gha_get_run_logsC | Fetch logs for a workflow run |
| gha_trigger_workflowC | Trigger a workflow_dispatch event |
| gha_rerun_workflowC | Re-run a workflow |
| gha_cancel_runC | Cancel a running workflow |
| gha_set_workflow_stateC | Enable or disable a workflow |
| gha_diagnose_failureB | Analyze a failed workflow run (with optional AI diagnosis) |
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 10 tools
Every tool has a clearly distinct purpose targeting specific GitHub Actions operations. Tools like gha_cancel_run, gha_rerun_workflow, and gha_trigger_workflow handle different workflow lifecycle stages, while gha_get_run, gha_get_run_logs, and gha_diagnose_failure provide distinct types of run information. There is no functional overlap that would cause agent confusion.
All tools follow a perfect gha_verb_noun naming pattern with consistent snake_case throughout. The prefix 'gha_' clearly identifies the domain, and verbs like 'cancel', 'get', 'list', 'rerun', 'set', and 'trigger' are consistently applied to appropriate nouns like 'run', 'workflow', and 'logs'.
With 10 tools, this server is well-scoped for GitHub Actions management. The count covers core operations without bloat, including workflow listing/management, run monitoring/control, and diagnostic capabilities. Each tool earns its place in providing a complete surface for the domain.
The toolset provides complete lifecycle coverage for GitHub Actions workflows. It includes discovery (list_workflows, list_runs), inspection (get_workflow, get_run, get_run_logs), control (trigger_workflow, rerun_workflow, cancel_run, set_workflow_state), and diagnostics (diagnose_failure). No obvious gaps exist for the stated purpose.