home / mcp / github action trigger mcp server

GitHub Action Trigger MCP Server

Provides MCP endpoints to fetch GitHub Actions data, trigger workflows, fetch releases, and auto-merge PRs.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "nextdriveioe-github-action-trigger-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nextdrive/github-action-trigger-mcp"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
      }
    }
  }
}

You can run a focused MCP server that interacts with GitHub Actions to fetch actions, inspect actions, trigger workflows, fetch releases, and enable auto-merge on PRs. This server lets you integrate GitHub Actions data and workflows into your MCP-enabled automation workflows, empowering you to discover, trigger, and manage Actions and releases directly from your tooling.

How to use

You use an MCP client to talk to the GitHub Action Trigger MCP server. From your client, call the available tools to list Actions in a repo, inspect a specific Action, trigger workflow_dispatch events, fetch recent releases, and enable auto-merge on pull requests. You supply the required parameters such as repository owner, repository name, and workflow identifiers, plus optional tokens when accessing private data or triggering workflows.

How to install

Prerequisites: Node.js installed on your system. You may also use a package manager to install JavaScript tooling.

{
  "mcpServers": {
    "github_action_trigger_mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nextdrive/github-action-trigger-mcp"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
      }
    }
  }
}

Local installation

If you prefer to install and run locally, install the MCP package globally and configure your client to point to the local server.

npm install -g @nextdrive/github-action-trigger-mcp
```

Then configure your Claude Desktop client with the local runtime, for example:

```
{
  "mcpServers": {
    "github_action_trigger_mcp": {
      "command": "@nextdrive/github-action-trigger-mcp",
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
      }
    }
  }
}

GitHub token configuration

To access the GitHub API for private repositories or to trigger workflows, configure a GitHub personal access token. You can set the token directly in your client’s configuration or via environment variables.

Development and debugging

For development and debugging, you can run standard build and test workflows, then use MCP Inspector to connect to and inspect the running MCP server.

Available tools

get_github_actions

Fetch available GitHub Actions for a repository. Requires owner and repo; token optional for private repos or higher API rate limits. Returns a list with IDs, names, paths, state, URLs, and content.

get_github_action

Fetch detailed information about a specific GitHub Action, including inputs and their requirements. Requires owner and repo, optional path, ref, and token.

trigger_github_action

Trigger a GitHub workflow using workflow_dispatch and pass inputs. Requires owner, repo, and workflow_id; supports ref, inputs, and token.

get_github_release

Retrieve the latest two releases for a repository. Requires owner and repo; token optional.

enable_pull_request_automerge

Enable auto-merge for a specific pull request using a specified merge method. Requires owner, repo, and pull_number; supports merge_method and token.