GitHub Actions MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token with appropriate permissions (repo, workflow, contents:read, contents:write, actions:read, actions:write) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_workflowC | Create a new GitHub Actions workflow file |
| list_workflowsB | List workflows in a GitHub repository |
| get_workflowC | Get details of a specific workflow |
| get_workflow_usageC | Get usage statistics of a workflow |
| list_workflow_runsC | List all workflow runs for a repository or specific workflow |
| get_workflow_runC | Get details of a specific workflow run |
| get_workflow_run_jobsC | Get jobs for a specific workflow run |
| trigger_workflowC | Trigger a workflow run |
| cancel_workflow_runC | Cancel a workflow run |
| rerun_workflowC | Re-run a workflow run |
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
Each tool has a clearly distinct purpose targeting specific GitHub Actions resources and actions, with no overlap. For example, list_workflows enumerates workflows, get_workflow retrieves details, create_workflow adds new ones, and trigger_workflow initiates runs, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case, such as list_workflows, get_workflow_run, and cancel_workflow_run. This predictability aids agents in understanding and using the toolset effectively without confusion from mixed conventions.
With 10 tools, the server is well-scoped for managing GitHub Actions workflows, covering essential operations like listing, creating, triggering, and monitoring runs. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset provides complete CRUD and lifecycle coverage for GitHub Actions, including create_workflow, list_workflows, get_workflow, trigger_workflow, rerun_workflow, cancel_workflow_run, and monitoring via get_workflow_run and get_workflow_usage, with no obvious gaps or dead ends.