Server facts
github-action-trigger-mcp
Project
- Author
- nextDriveIoE
- License
- Not specified
- Category
- Version Control
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- github action
- github integration
- mcp server
Overview
GitHub Actions discovery and workflow dispatch sit at the center of github-action-trigger-mcp. Developers can use get_github_actions to list repository workflows with their identifiers, paths, states, URLs, and definition content. For inspecting an individual action, get_github_action exposes descriptive metadata and input requirements, with options to select a definition path and Git reference. This separates reviewing available workflows from examining how a particular action expects to be configured.
Execution uses trigger_github_action, which accepts a workflow identifier or filename, a target reference, and workflow inputs. The target workflow must support workflow_dispatch, supplied inputs must match its definition, and the token needs workflow scope. Alongside dispatch, get_github_release retrieves the latest 2 repository releases, while enable_pull_request_automerge enables automatic merging for a chosen pull request once required checks pass. The TypeScript implementation communicates over stdio, and the README provides Claude Desktop setup. Token configuration can come from client settings, an environment variable, or a local configuration file, including access to private repositories.
github-action-trigger-mcp setup notes
- github-action-trigger-mcp records stdio only; confirm a network transport upstream before planning remote access.
- github-action-trigger-mcp has no recorded license; confirm reuse terms in its repository.