gh-release-mcp
Related Servers
Alternatives to gh-release-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA single static Go binary that exposes GitHub operations (repos, branches, commits, file contents, issues, PRs, and search) as MCP tools, enabling agents to read and write GitHub data with no runtime dependencies.MIT
- AlicenseNot gradedqualityBmaintenanceEnables remote access to GitHub REST and GraphQL APIs via dynamically generated and universal tools, with support for Actions log retrieval, schema introspection, and read-only Git clone/fetch.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to remotely execute shell commands and transfer files on SSH hosts, including jump-host tunneling, background tasks, resumable transfers, and optional approval of destructive commands, while SSH credentials remain in the local process. It runs over stdio or a streamable HTTP daemon and supports auditing, allow/deny lists, and multiple authentication methods.ISC
- AlicenseNot gradedqualityCmaintenanceEnables LLM hosts to perform scoped GitHub operations over stdio, including repository intelligence, pull request lifecycle and diff inspection, and commit history queries. It exposes 12 FastMCP tools backed by PyGithub for repository, PR, and commit workflows.MIT
- FlicenseBqualityCmaintenanceEnables parallel agent tasks on disposable Arch Linux drones by providing a local stdio gateway for batch job submission, status monitoring, log retrieval, artifact fetching, and cancellation across SSH-connected runners.13-
- AlicenseNot gradedqualityDmaintenanceProvides secure filesystem operations, HTTP fetching with SSRF protection, JSON validation, artifact logging, and optional Redis key-value storage through both stdio and HTTP transports. Features production-ready security controls including sandbox enforcement, allowlist validation, and comprehensive input validation.Apache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists metadata about assets, the other downloads asset content. An agent can easily tell which to invoke based on whether it needs information or the file itself.
Both names follow a clean verb_noun pattern (list_release_assets, download_release_asset) with consistent snake_case and a shared 'release_asset' subject. There is no stylistic deviation.
Two tools is very thin for a server named gh-release-mcp, which implies release management rather than just asset handling. The surface feels like a narrow slice of the domain rather than a complete toolkit.
The server covers listing and downloading release assets but omits core release lifecycle operations: listing releases, creating/deleting releases, and uploading assets. Agents needing anything beyond download will hit dead ends.