F
licenseNot graded
qualityC
maintenanceEnables users to read and manage GitHub repositories through MCP, with destructive operations gated behind explicit confirmation and dry-run previews.
1
-
GitHub Actions MCP Server
by lockround
Related Servers
Alternatives to GitHub Actions MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables managing GitHub repositories, files, and user information through MCP, with support for creating, updating, and deleting repository contents, as well as fetching user profiles.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to manage GitHub repositories and issues and trigger repository dispatch events via tools and a REST API.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables management of multiple N8N workflow automation instances through MCP. Supports listing, creating, updating, deleting, executing workflows and monitoring their executions across different N8N environments.54 npmMIT
- AlicenseCqualityFmaintenanceAn MCP server that enables AI assistants to manage GitHub Actions workflows by providing tools for listing, viewing, triggering, canceling, and rerunning workflows through the GitHub API.924 npm41MIT
TDQS
A3.6/5.0
Scored across 7 tools
Disambiguation4/5
Most tools target clearly distinct resources (workflow definitions, workflow runs, repo parsing). However, trigger-workflow and trigger-repository-dispatch can both start workflows, and get-workflow vs get-workflow-run could be confused without reading descriptions carefully.
Naming Consistency5/5
All tool names follow a consistent lower-case hyphenated verb-object pattern, such as list-workflows, trigger-workflow, and cancel-workflow-run. There is no mixing of naming conventions or vague verbs.
Tool Count5/5
Seven tools is a well-scoped size for a GitHub Actions-focused server. Each tool serves a distinct operational purpose without unnecessary bloat or redundancy.
Completeness4/5
The server covers core workflow discovery, triggering, run status, and cancellation. Missing operations like listing all workflow runs, re-running workflows, or fetching logs create minor gaps, but the main lifecycle is reasonably represented.
Maintenance
ActivityMaintained
ResponsivenessNo issues