Catalog discovery
Browse and launch containerized MCP servers from the Docker MCP Catalog.
Documentation ↗MCP server / cloud & infrastructure / source-linked
Docker MCP Toolkit
Docker MCP Toolkit is a Docker Desktop management layer for discovering, configuring, and running containerized MCP servers. It organizes servers into profiles, handles OAuth, and adds container isolation, resource limits, signatures/SBOMs, filesystem restrictions, and request interception. MCP Gateway is an invite-only governance feature; the Toolkit itself is the normal desktop path.
Before you choose.
Identify the implementation and the job it supports.
Docker MCP Toolkit is a Docker Desktop management layer for discovering, configuring, and running containerized MCP servers. It organizes servers into profiles, handles OAuth, and adds container isolation, resource limits, signatures/SBOMs, filesystem restrictions, and request interception. MCP Gateway is an invite-only governance feature; the Toolkit itself is the normal desktop path.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Local Docker Gateway; clients connect through the Toolkit profile
- Authentication
- OAuth is handled by Docker Desktop for supported services; server-specific credentials are injected by the Toolkit.
Use Docker Desktop 4.62+ with MCP Toolkit, browse the Catalog, add a server to a profile, configure OAuth or credentials, then connect the profile to the MCP client.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
Docker Desktop UI is the recommended setup; advanced users can install the docker-mcp CLI plugin and run docker mcp --help.What it actually exposes.
Concrete capabilities with maintainer sources.
Profiles and gateway
Maintain separate project/environment server collections and route clients through a gateway.
Documentation ↗Runtime security
Use signed images/SBOMs, CPU/memory limits, restricted filesystem mounts, secret interception, and OAuth credential handling.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Docker MCP Toolkit initial adoption pains
An early adopter liked the concept but found tool grouping, catalog size, and incomplete coverage difficult enough to stop using the toolkit temporarily.
“Toolsets require exact tool names, the combined catalog inflates available tools, and the author reverted after a few days.”Open community source ↗
Thoughts on docker mcp toolkit?
A user values centralized secrets and container management but reports client compatibility gaps and a still-small catalog.
“It mostly worked, but Windsurf did not see MongoDB tools even though Docker MCP Toolkit was configured.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Reproducible MCP workspace
Suggested evaluation, not an observed test result.
- Create a profile for a project and add only the servers required for its workflow.
- Configure OAuth/credentials in Docker Desktop and verify container/image provenance.
- Connect the profile to the client and record the enabled server list for review.
What to inspect: An isolated, repeatable MCP runtime profile with a clear credential and filesystem boundary. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Docker Desktop 4.62+ is required for the documented Toolkit interface; earlier versions have a different UI.
Boundary reference ↗MCP Gateway governance is invite-only, so its centralized policy features may not be available to every Toolkit user.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
An isolated, repeatable MCP runtime profile with a clear credential and filesystem boundary. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Composio MCP | Choose for hosted per-user SaaS sessions and dynamic tool policy. | Docker focuses on local container isolation; Composio focuses on hosted integrations and auth sessions. Documentation ↗ |
| Cloudflare MCP | Choose for managed production edge APIs rather than local MCP runtime orchestration. | Cloudflare is remote; Docker adds local runtime control. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Does Toolkit require manual dependency management?
Docker documents zero manual setup for catalog servers because they run as containers.
Documentation ↗
What does a profile do?
A profile is a named collection of servers/configuration made available to clients.
Documentation ↗
Source trail.
Maintainer documentation used in this record.