GitHub Actions MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub token with repo scope (workflow scope for triggering workflows) |
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 |
|---|---|
| parse-github-repoA | Parse a GitHub URL or "owner/repo" string into structured owner and repo fields. |
| list-workflowsA | List all GitHub Actions workflows for a repository. |
| get-workflowC | Get details of a specific GitHub Actions workflow by ID or filename. |
| trigger-workflowB | Trigger a GitHub Actions workflow via workflow_dispatch event. |
| get-workflow-runB | Get the latest or a specific GitHub Actions workflow run status. |
| cancel-workflow-runA | Cancel a running GitHub Actions workflow. |
| trigger-repository-dispatchC | Trigger a repository_dispatch event to start a workflow. |
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 7 tools
Most tools target clearly distinct resources (workflow definitions, workflow runs, repo parsing). However, trigger-workflow and trigger-repository-dispatch can both start workflows, and get-workflow vs get-workflow-run could be confused without reading descriptions carefully.
All tool names follow a consistent lower-case hyphenated verb-object pattern, such as list-workflows, trigger-workflow, and cancel-workflow-run. There is no mixing of naming conventions or vague verbs.
Seven tools is a well-scoped size for a GitHub Actions-focused server. Each tool serves a distinct operational purpose without unnecessary bloat or redundancy.
The server covers core workflow discovery, triggering, run status, and cancellation. Missing operations like listing all workflow runs, re-running workflows, or fetching logs create minor gaps, but the main lifecycle is reasonably represented.