act-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACT_BIN | No | Path to the act binary (default: act) | act |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsA | List .github/workflows/*.yml files and their job names |
| run_jobA | Run a specific job via act -j , returns exitCode and captured logs |
| get_logsA | Return cached stdout+stderr from the most recent run_job call |
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 3 tools
Each tool targets a distinct action: listing workflows, running a job, and retrieving logs. There is no functional overlap between them.
All tool names follow a consistent verb_noun pattern using snake_case: list_workflows, run_job, get_logs. No deviations.
Three tools is within the typical well-scoped range (3-15) and each tool serves a necessary and clear purpose in the workflow.
The tool set covers the full lifecycle for the server's domain: listing available workflows, executing a job, and retrieving results. No obvious gaps are present.