CNB Remote MCP
Related Servers
Alternatives to CNB Remote MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to manage self-hosted Git repositories from ChatGPT and compatible Codex clients via OAuth-secured connections, with independent browser approval for write actions. Supports repository, file, branch, issue, pull request, release, and workflow operations while excluding administrative tools.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.26 npmMIT
- FlicenseNot gradedqualityDmaintenanceBridges ChatGPT to GitHub with full write access, enabling repository management, file operations, and pull request creation.-
- AlicenseBqualityCmaintenanceEnables AI agents to read repositories, manage issues, inspect CI/CD workflow runs, create branches, commit files, and open pull requests on a self-hosted Gitea instance.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI applications to retrieve GitHub repository information, manage issues, and monitor workflow statuses through the GitHub REST API.-
- AlicenseBqualityCmaintenanceEnables compatible AI clients to open, inspect, edit, test, commit, and manage GitHub repositories through local STDIO or authenticated remote Streamable HTTP, including issues, pull requests, workflows, and repository creation.30MIT
TDQS
Scored across 29 tools
Tools are grouped by resource prefix (repo_*, issue_*, pr_*, build_*, npc_*) and most have a single distinct action, so an agent can pick correctly in the common case. A few pairs are close: repo_commit_statuses vs pr_checks, build_status vs npc_status, and pr_commits vs pr_files all surface overlapping CI/commit data, though the descriptions do enough to separate them.
Nearly all tools follow a resource_action snake_case convention (repo_list, issue_get, pr_review_list, build_stage_logs), which is highly predictable. Minor deviations exist: whoami and pr_commits (verb/plural noun without action) and a couple of prefix irregularities like repo_file_read vs repo_tree_list.
At 29 tools this is above the comfortable range for what is essentially a read-only repository browsing surface, and several list/get pairs feel granular enough to be merged. The npc_* group in particular adds scope that inflates the set without adding much distinct capability.
Read coverage is thorough: repos, files, commits, diffs, branches, tags, issues, PRs, reviews, builds, and logs are all reachable. However, there is no write/lifecycle operation anywhere — no create issue, open PR, comment, merge, or branch creation — so workflows dead-end at read-only inspection.