A
licenseNot graded
qualityD
maintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.
379 npm
ISC
GitHub Actions MCP Server
by ko1ynnky
Related Servers
Alternatives to GitHub Actions MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps around the GitHub CLI tool, allowing AI assistants to interact with GitHub repositories through commands for pull requests, issues, and repository operations.8 npmMIT
- FlicenseNot gradedqualityCmaintenanceA custom MCP server that lets AI assistants interact with GitHub accounts, offering tools for repository creation, file viewing, code search, and issue management.-
- FlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to list GitHub repositories for a user or organization and list directories within a repository via the GitHub REST API.2-
- FlicenseAqualityCmaintenanceMCP server that lets AI agents interact with GitHub using natural language, supporting operations like creating repositories, issues, and commits.5-
- AlicenseBqualityCmaintenanceA comprehensive MCP server that exposes 73 GitHub API tools for managing repositories, pull requests, issues, actions, releases, search, and more, enabling natural language control of GitHub.73MIT
TDQS
C2.1/5.0
Scored across 9 tools
Disambiguation5/5
Every tool has a clearly distinct purpose targeting specific GitHub Actions resources and operations. The naming clearly indicates whether tools retrieve information (get_, list_), trigger actions (trigger_, rerun_, cancel_), or access different aspects (workflows, runs, jobs, usage). There is no ambiguity or overlap in functionality.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with perfect uniformity. The verbs (cancel, get, list, rerun, trigger) are consistently applied to clearly defined nouns (workflow, workflow_run, workflow_run_jobs, etc.). There are no deviations in naming conventions or styles.
Tool Count5/5
With 9 tools, this server is well-scoped for managing GitHub Actions workflows. The count is appropriate for covering core operations like listing, retrieving, triggering, and managing workflow runs without being overwhelming. Each tool serves a distinct purpose that earns its place in the set.
Completeness4/5
The tool surface provides excellent coverage for the GitHub Actions domain with operations for listing, retrieving, triggering, rerunning, and canceling workflows and runs. Minor gaps might include tools for managing workflow files or secrets, but the core lifecycle operations are well-covered for typical agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues