act-testing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACT_BINARY | No | Path to the act binary (default: 'act' found in PATH) | |
| PROJECT_ROOT | No | Override the project root directory (default: current working directory) |
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 all available GitHub Actions workflows in the repository |
| run_workflowB | Run a GitHub Actions workflow locally using act |
| validate_workflowB | Validate a workflow file syntax and structure |
| act_doctorA | Check act configuration and Docker setup |
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 4 tools
Each tool targets a distinct action: checking setup, listing workflows, running them, and validating syntax. No overlap in purposes.
All tools follow a consistent verb_noun pattern (e.g., list_workflows, run_workflow) with 'act_doctor' as a slight exception but still clear.
4 tools is well-scoped for the server's purpose of testing GitHub Actions workflows locally, covering essential operations without excess.
Covers the key operations: setup check, listing, running, and validation. Minor gap might be configuring act, but the set is functional for typical use.