act-mcp
Allows running GitHub Actions workflows locally via act, providing tools to list workflows, run jobs, and retrieve logs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@act-mcplist workflows in current repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
act-mcp
MCP stdio server exposing three tools for running GitHub Actions locally via act.
Peer dependency: act
act must be installed and in PATH:
# macOS
brew install act
# Linux
curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bashRelated MCP server: AI Code Review MCP Server
MCP Tools
list_workflows
Globs .github/workflows/*.yml and returns job names from each file.
Field | Type | Description |
|
| Repo root (default: |
Returns: Array<{ file: string, jobs: string[] }>
run_job
Spawns act -j <jobName>, captures stdout+stderr, caches logs.
Field | Type | Description |
|
| Job ID (key under |
|
| Repo root (default: |
Returns: { exitCode: number, logs: string }
get_logs
Returns logs cached by the most recent run_job call.
Returns: { logs: string | null }
Agent loop
list_workflows → pick failing job
run_job → read exitCode + logs
get_logs → inspect failure output
(patch YAML)
run_job → verify fixMCP client config (Claude Desktop)
{
"mcpServers": {
"act-mcp": {
"command": "npx",
"args": ["act-mcp"]
}
}
}Or point cwd at a specific repo:
{
"mcpServers": {
"act-mcp": {
"command": "npx",
"args": ["act-mcp"],
"env": {}
}
}
}Pass cwd as a tool argument at call time:
{ "name": "list_workflows", "arguments": { "cwd": "/path/to/repo" } }Development
npm install
npm run build # tsc → dist/
npm test # vitest (uses mock act binary, no act required)
npm run dev # run via tsx without buildingEnvironment variables
Variable | Default | Description |
|
| Path to the act binary (useful for testing) |
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Isco0819/act-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server