GitHub Codespaces MCP
Related Servers
Alternatives to GitHub Codespaces MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to turn local projects into persistent workspaces, providing file editing, command execution, Git integration, and cross-session history management.-
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.06MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.31 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.4Apache 2.0
- AlicenseAqualityDmaintenanceProvides secure access to containerized build environments for software projects, enabling AI assistants to execute builds, run tests, manage git operations, and inspect build artifacts without requiring local installation of dependencies.6MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to develop within a local project workspace by reading and modifying files, running commands and tests, checking Git state, and persisting progress as history sessions that can be restored in later conversations.-
TDQS
Scored across 12 tools
Each tool maps to a distinct stage of the Codespaces workflow (check, list, bind, prepare, probe, inspect, submit, get, logs, cancel, download, release). The only mild overlap is between codespace_prepare and runner_probe, which both involve the bundled runner on the bound Codespace, but the descriptions distinguish install-and-probe from the ten-second survival diagnostic.
All 12 tools follow a consistent noun_verb prefix pattern (environment_check, codespace_list, project_bind, job_submit, artifact_download, codespace_release, etc.). There is no mixing of camelCase or divergent verb styles.
12 tools sit squarely in the well-scoped 3-15 range. Every tool corresponds to a needed action in the binding/prepare/job/artifact/release lifecycle with no redundant entries.
The surface covers the full non-destructive lifecycle: identity check, binding, prepare/probe, job submit/get/logs/cancel, artifact download, and release. Codespace creation and deletion are intentionally excluded per the descriptions, which is a reasonable design boundary but leaves those operations as dead ends for users needing them.