Docker Claude Plugins
docker-claude-plugins is a Claude Code plugin for the Build phase that officially integrates Docker Desktop’s MCP toolkit and containerized MCP server access.
by docker · github.com/docker/claude-plugins
Add Docker’s official Claude Code plugin so your agent can use the MCP toolkit and containerized dev environments through Docker Desktop.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install docker-claude-plugins@docker/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:docker/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:docker/claude-plugins").
What it does
docker-claude-plugins is Docker’s official Claude Code integration: a single plugin that connects your coding agent to the Docker Desktop MCP toolkit so tools run inside managed containers instead of polluting your host. For solo builders, that means you can spin up MCP servers with clearer boundaries, reuse Desktop’s gateway, and keep dependencies isolated while you iterate on agents, APIs, or CLIs. The listing stresses enabling MCP on Docker Desktop first—this is an integration step, not a turnkey app generator. It fits the Build phase when you are standardizing how Claude Code reaches databases, browsers, or custom MCP images. It is narrower than a full DevOps suite: no substitute for production orchestration docs, but valuable when every experiment used to break your local Node or Python install. Pair it with your own skill prompts once the gateway is live.
Highlights
- Official docker/claude-plugins repository with one focused plugin
- Docker Desktop MCP toolkit integration for Claude Code
- Gateway pattern for enabling containerized MCP servers
- Requires Docker Desktop with MCP tooling enabled
- Suited to local, containerized agent tool access rather than cloud-only workflows
Why builders use it
Agents that install MCP tools directly on the host create messy, irreproducible dev machines and fragile toolchains.
After install, Claude Code can route MCP tool calls through Docker Desktop’s containerized gateway for cleaner, repeatable local integrations.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 15 stars, 0 votes.
FAQ
Who is docker-claude-plugins for?
Claude Code users on Docker Desktop who want official, container-backed MCP server access via the MCP toolkit.
When should I use docker-claude-plugins?
Use it during Build when you are enabling agent tools that should run in containers rather than on your bare-metal environment.
How do I add docker-claude-plugins to my agent?
Install the plugin from docker/claude-plugins, ensure Docker Desktop is installed with MCP toolkit enabled, then register the plugin in Claude Code per Docker’s README.
Comments
Share how you use docker-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.