content/manuals/ai/mcp-catalog-and-toolkit/catalog.md
{{< summary-bar feature_name="Docker MCP Catalog" >}}
The Docker MCP Catalog is a curated collection of verified MCP servers, packaged as Docker images and distributed through Docker Hub. It solves common challenges with running MCP servers locally: environment conflicts, setup complexity, and security concerns.
The catalog serves as the source of available MCP servers. When you add servers to your profiles, you select them from the catalog. Each server runs as an isolated container, making it portable and consistent across different environments.
[!NOTE] E2B sandboxes now include direct access to the Docker MCP Catalog, giving developers access to over 200 tools and services to seamlessly build and run AI agents. For more information, see E2B Sandboxes.
The Docker MCP Catalog includes:
The catalog contains two types of servers based on where they run:
Local servers run as containers on your machine. They work offline once downloaded and offer predictable performance and complete data privacy. Docker builds and signs all local servers in the catalog.
Remote servers run on the provider's infrastructure and connect to external services. Many remote servers use OAuth authentication, which the MCP Toolkit handles automatically through your browser.
Browse available MCP servers at hub.docker.com/mcp or directly in Docker Desktop:
To add a server from the catalog to a profile:
For step-by-step instructions and client connection, see Get started with MCP Toolkit or MCP Profiles.
Custom catalogs let you curate focused collections of servers for your team or organization. Instead of exposing all 300+ servers in the Docker catalog, you define exactly which servers are available.
Common use cases:
Custom catalogs work particularly well with
Dynamic MCP, where agents discover
and add MCP servers on-demand during conversations. When you run the gateway
with a custom catalog, the mcp-find tool searches only within that catalog.
If your catalog contains 20 servers instead of 300+, agents work within that
focused set, discovering and enabling tools as needed without manual
configuration each time.
If someone on your team has created and published a catalog, you can import it using its OCI registry reference.
In Docker Desktop:
registry.example.com/mcp/team-catalog:latest).Using the CLI:
$ docker mcp catalog pull <oci-reference>
Once imported, the catalog appears alongside the Docker catalog and you can add its servers to your profiles.
Creating and managing custom catalogs requires the CLI. See Custom catalogs in the CLI how-to for step-by-step instructions, including:
The MCP server registry is available at https://github.com/docker/mcp-registry. To submit an MCP server, follow the contributing guidelines.
When your pull request is reviewed and approved, your MCP server is available within 24 hours on:
mcp namespace (for MCP
servers built by Docker).