Skip to main content
Glama

GitHub Action Trigger MCP Server

by nextDriveIoE

trigger_github_action

Trigger GitHub workflow dispatch events by specifying repository details, workflow ID, and custom inputs for automated execution and integration.

Instructions

Trigger a GitHub workflow dispatch event with custom inputs

Input Schema

NameRequiredDescriptionDefault
inputsNoInputs to pass to the workflow (must match the workflow's defined inputs)
ownerYesOwner of the repository (username or organization)
refNoThe git reference to trigger the workflow on (default: main)
repoYesName of the repository
tokenNoGitHub personal access token (must have workflow scope)
workflow_idYesThe ID or filename of the workflow to trigger

Input Schema (JSON Schema)

{ "properties": { "inputs": { "description": "Inputs to pass to the workflow (must match the workflow's defined inputs)", "type": "object" }, "owner": { "description": "Owner of the repository (username or organization)", "type": "string" }, "ref": { "description": "The git reference to trigger the workflow on (default: main)", "type": "string" }, "repo": { "description": "Name of the repository", "type": "string" }, "token": { "description": "GitHub personal access token (must have workflow scope)", "type": "string" }, "workflow_id": { "description": "The ID or filename of the workflow to trigger", "type": "string" } }, "required": [ "owner", "repo", "workflow_id" ], "type": "object" }

You must be authenticated.

Other Tools from GitHub Action Trigger MCP Server

Related Tools

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/nextDriveIoE/github-action-trigger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server