| FMRS | 29 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 5 / 20 | 13 / 20 |
|---|
| Security and permissions | 5 / 20 | 14 / 20 |
|---|
| Maintenance | 6 / 20 | 18 / 20 |
|---|
| Documentation | 6 / 20 | 17 / 20 |
|---|
| Setup experience | 7 / 20 | 14 / 20 |
|---|
| Best for | - Users of AI coding tools (Claude, Cursor, etc.) who want to reduce token usage.
- Agents that need reliable, unambiguous Docker output for automated decision-making.
- Developers using Docker as part of their infrastructure and wanting MCP integration in their workflow.
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Users requiring interactive terminal control or full Docker CLI features (like attach, exec -it).
- Users unfamiliar with MCP configuration or Node.js environments.
- Users needing raw output from the Docker daemon, not structured data.
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Permissions to execute Docker commands, such as access to Docker socket or daemon (depending on environment).
- Network access for npx to download npm packages or Docker images (if pulling during builds).
- Filesystem access to read Dockerfiles or build contexts (if applicable).
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - Running Docker commands may affect containers, images, or builds, e.g., removing containers or modifying images.
- Misconfiguration or network issues can cause Docker commands to fail, and agents may receive incomplete structured data.
- Using npx may introduce supply-chain risks, as remote code is downloaded and executed on each invocation.
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, Roo Code, Codex, Gemini CLI, Zed, Continue | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 5 | 15 |
|---|