Skip to main content
Glama

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 bash

Related 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

cwd

string?

Repo root (default: process.cwd())

Returns: Array<{ file: string, jobs: string[] }>

run_job

Spawns act -j <jobName>, captures stdout+stderr, caches logs.

Field

Type

Description

jobName

string

Job ID (key under jobs: in the YAML)

cwd

string?

Repo root (default: process.cwd())

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 fix

MCP 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 building

Environment variables

Variable

Default

Description

ACT_BIN

act

Path to the act binary (useful for testing)

Available Tools

3 tools
get_logsA

Return cached stdout+stderr from the most recent run_job call

Inputs: no named parameters.

list_workflowsA

List .github/workflows/*.yml files and their job names

Inputs: cwd.

run_jobA

Run a specific job via act -j , returns exitCode and captured logs

Inputs: jobName (required), cwd.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action: listing workflows, running a job, and retrieving logs. There is no functional overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: list_workflows, run_job, get_logs. No deviations.

    Tool Count5/5

    Three tools is within the typical well-scoped range (3-15) and each tool serves a necessary and clear purpose in the workflow.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Connects AI assistants to GitHub Actions workflows to monitor CI/CD pipelines, view run logs, diagnose failures, and optionally trigger or manage workflows with granular permission controls.
      10
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      Integrates GitHub repository management and local file system access to enable AI agents to perform code reviews and manage pull requests. It provides tools for listing repositories, retrieving PR diffs, and searching or reading files within a specified workspace.
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables managing and debugging Azure Logic Apps through natural language, with tools for listing, debugging, creating, updating, and deleting workflows.
      40
      123 npm
      7
      MIT