Skip to content

Commit ad0efc2

Browse files
dvdksndvdksn
committed
mcp: add docs on custom MCP catalogs
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
1 parent b239fd1 commit ad0efc2

2 files changed

Lines changed: 215 additions & 114 deletions

File tree

‎content/manuals/ai/mcp-catalog-and-toolkit/_index.md‎

Lines changed: 59 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -11,30 +11,38 @@ weight: 10
1111
description: Learn about Docker's MCP catalog on Docker Hub
1212
keywords: Docker, ai, mcp servers, ai agents, extension, docker desktop, llm, docker hub
1313
grid:
14-
- title: Get started with MCP Toolkit
15-
description: Learn how to quickly install and use the MCP Toolkit to set up servers and clients.
16-
icon: explore
17-
link: /ai/mcp-catalog-and-toolkit/get-started/
18-
- title: MCP Catalog
19-
description: Learn about the benefits of the MCP Catalog, how you can use it, and how you can contribute
20-
icon: hub
21-
link: /ai/mcp-catalog-and-toolkit/catalog/
22-
- title: MCP Toolkit
23-
description: Learn about the MCP Toolkit to manage MCP servers and clients
24-
icon: /icons/toolkit.svg
25-
link: /ai/mcp-catalog-and-toolkit/toolkit/
26-
- title: Dynamic MCP
27-
description: Discover and add MCP servers on-demand using natural language
28-
icon: search
29-
link: /ai/mcp-catalog-and-toolkit/dynamic-mcp/
30-
- title: MCP Gateway
31-
description: Learn about the underlying technology that powers the MCP Toolkit
32-
icon: developer_board
33-
link: /ai/mcp-catalog-and-toolkit/mcp-gateway/
34-
- title: Docker Hub MCP server
35-
description: Explore about the Docker Hub server for searching images, managing repositories, and more
36-
icon: device_hub
37-
link: /ai/mcp-catalog-and-toolkit/hub-mcp/
14+
- title: Get started with MCP Toolkit
15+
description: Learn how to quickly install and use the MCP Toolkit to set up servers and clients.
16+
icon: explore
17+
link: /ai/mcp-catalog-and-toolkit/get-started/
18+
- title: MCP Catalog
19+
description: Browse Docker's curated collection of verified MCP servers
20+
icon: hub
21+
link: /ai/mcp-catalog-and-toolkit/catalog/
22+
- title: MCP Toolkit
23+
description: Learn about the MCP Toolkit to manage MCP servers and clients
24+
icon: /icons/toolkit.svg
25+
link: /ai/mcp-catalog-and-toolkit/toolkit/
26+
- title: MCP Gateway
27+
description: Learn about the underlying technology that powers the MCP Toolkit
28+
icon: developer_board
29+
link: /ai/mcp-catalog-and-toolkit/mcp-gateway/
30+
- title: Dynamic MCP
31+
description: Discover and add MCP servers on-demand using natural language
32+
icon: search
33+
link: /ai/mcp-catalog-and-toolkit/dynamic-mcp/
34+
- title: Docker Hub MCP server
35+
description: Use the Docker Hub MCP server to search images and manage repositories
36+
icon: device_hub
37+
link: /ai/mcp-catalog-and-toolkit/hub-mcp/
38+
- title: Security FAQs
39+
description: Common questions about MCP security, credentials, and server verification
40+
icon: security
41+
link: /ai/mcp-catalog-and-toolkit/faqs/
42+
- title: E2B sandboxes
43+
description: Cloud sandboxes for AI agents with built-in MCP Catalog access
44+
icon: cloud
45+
link: /ai/mcp-catalog-and-toolkit/e2b-sandboxes/
3846
---
3947

4048
{{< summary-bar feature_name="Docker MCP Catalog and Toolkit" >}}
@@ -45,47 +53,39 @@ and data sources. By connecting LLMs to local development tools, databases,
4553
APIs, and other resources, MCP extends their capabilities beyond their base
4654
training.
4755

48-
Through a client-server architecture, applications such as Claude, ChatGPT, and
49-
[Gordon](/manuals/ai/gordon/_index.md) act as clients that send requests to MCP
50-
servers, which then process these requests and deliver the necessary context to
51-
AI models.
52-
53-
MCP servers extend the utility of AI applications, but running servers locally
54-
also presents several operational challenges. Typically, servers must be
55-
installed directly on your machine and configured individually for each
56-
application. Running untrusted code locally requires careful vetting, and the
57-
responsibility of keeping servers up-to-date and resolving environment
58-
conflicts falls on the user.
56+
The challenge is that running MCP servers locally creates operational friction.
57+
Each server requires separate installation and configuration for every
58+
application you use. You run untrusted code directly on your machine, manage
59+
updates manually, and troubleshoot dependency conflicts yourself. Configure a
60+
GitHub server for Claude, then configure it again for Cursor, and so on. Each
61+
time you manage credentials, permissions, and environment setup.
5962

6063
## Docker MCP features
6164

62-
Docker provides three integrated components that address the challenges of
63-
running local MCP servers:
64-
65-
MCP Catalog
66-
: A curated collection of verified MCP servers, packaged and distributed as
67-
container images via Docker Hub. All servers are versioned, come with full
68-
provenance and SBOM metadata, and are continuously maintained and updated with
69-
security patches.
70-
71-
MCP Toolkit
72-
: A graphical interface in Docker Desktop for discovering, configuring, and
73-
managing MCP servers. The Toolkit provides a unified way to search for servers,
74-
handle authentication, and connect them to AI applications.
65+
Docker solves these challenges by packaging MCP servers as containers and
66+
providing tools to manage them centrally. Docker provides three integrated
67+
components: the [MCP Catalog](/ai/mcp-catalog-and-toolkit/catalog/) for
68+
discovering servers, the [MCP Gateway](/ai/mcp-catalog-and-toolkit/mcp-gateway/)
69+
for running them, and the [MCP Toolkit](/ai/mcp-catalog-and-toolkit/toolkit/)
70+
for managing everything through Docker Desktop.
7571

76-
MCP Gateway
77-
: The core open source component that powers the MCP Toolkit. The MCP Gateway
78-
manages MCP containers provides a unified endpoint that exposes your enabled
79-
servers to all AI applications you use.
72+
The [MCP Catalog](/ai/mcp-catalog-and-toolkit/catalog/) is where you find
73+
servers. Docker maintains 300+ verified servers, packaged as container images
74+
with versioning, provenance, and security updates. Servers run isolated in
75+
containers rather than directly on your machine. Organizations can create
76+
[custom catalogs](/ai/mcp-catalog-and-toolkit/catalog/#custom-catalogs) with
77+
approved servers for their teams.
8078

81-
This integrated approach ensures:
79+
The [MCP Gateway](/ai/mcp-catalog-and-toolkit/mcp-gateway/) runs your servers
80+
and routes requests from AI applications to the right server. It handles
81+
containerized servers, remote servers, authentication, and lifecycle
82+
management. Every AI application connects to the Gateway, which means you
83+
configure credentials and permissions once instead of per-application.
8284

83-
- Simplified discovery and setup of trusted MCP servers from a curated catalog
84-
of tools
85-
- Centralized configuration and authentication from within Docker Desktop
86-
- A secure, consistent execution environment by default
87-
- Improved performance since applications can share a single server runtime,
88-
compared to having to spin up duplicate servers for each application.
85+
The [MCP Toolkit](/ai/mcp-catalog-and-toolkit/toolkit/) provides a graphical
86+
interface in Docker Desktop for browsing catalogs, enabling servers, and
87+
connecting clients. You can also use the `docker mcp` CLI to manage everything
88+
from the terminal.
8989

9090
![MCP overview](./images/mcp-overview.svg)
9191

‎content/manuals/ai/mcp-catalog-and-toolkit/catalog.md‎

Lines changed: 156 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -1,86 +1,71 @@
11
---
22
title: Docker MCP Catalog
3-
linkTitle: MCP Catalog
3+
linkTitle: Catalog
44
description: Learn about the benefits of the MCP Catalog, how you can use it, and how you can contribute
55
keywords: docker hub, mcp, mcp servers, ai agents, catalog, docker
66
weight: 20
77
---
88

99
{{< summary-bar feature_name="Docker MCP Catalog" >}}
1010

11-
The [Docker MCP Catalog](https://hub.docker.com/mcp) is a centralized, trusted
12-
registry for discovering, sharing, and running MCP-compatible tools. Integrated
13-
with Docker Hub, it offers verified, versioned, and curated MCP servers
14-
packaged as Docker images. The catalog is also available in Docker Desktop.
11+
The [Docker MCP Catalog](https://hub.docker.com/mcp) is a curated collection of
12+
verified MCP servers, packaged as Docker images and distributed through Docker
13+
Hub. It solves common challenges with running MCP servers locally: environment
14+
conflicts, setup complexity, and security concerns.
1515

16-
The catalog solves common MCP server challenges:
17-
18-
- Environment conflicts. Tools often need specific runtimes that might clash
19-
with existing setups.
20-
- Lack of isolation. Traditional setups risk exposing the host system.
21-
- Setup complexity. Manual installation and configuration slow adoption.
22-
- Inconsistency across platforms. Tools might behave unpredictably on different
23-
operating systems.
24-
25-
With Docker, each MCP server runs as a self-contained container. This makes it
26-
portable, isolated, and consistent. You can launch tools instantly using the
27-
Docker CLI or Docker Desktop, without worrying about dependencies or
28-
compatibility.
29-
30-
## Key features
31-
32-
- Extensive collection of verified MCP servers in one place.
33-
- Publisher verification and versioned releases.
34-
- Pull-based distribution using Docker infrastructure.
35-
- Tools provided by partners such as New Relic, Stripe, Grafana, and more.
16+
The catalog serves as the source of available MCP servers. Each server runs as
17+
an isolated container, making it portable and consistent across different
18+
environments.
3619

3720
> [!NOTE]
3821
> E2B sandboxes now include direct access to the Docker MCP Catalog, giving developers
3922
> access to over 200 tools and services to seamlessly build and run AI agents. For
4023
> more information, see [E2B Sandboxes](sandboxes.md).
4124
42-
## How it works
43-
44-
Each tool in the MCP Catalog is packaged as a Docker image with metadata.
45-
46-
- Discover tools on Docker Hub under the `mcp/` namespace.
47-
- Connect tools to your preferred agents with simple configuration through the
48-
[MCP Toolkit](toolkit.md).
49-
- Pull and run tools using Docker Desktop or the CLI.
25+
## What's in the catalog
5026

51-
Each catalog entry displays:
27+
The Docker MCP Catalog includes:
5228

53-
- Tool description and metadata.
54-
- Version history.
55-
- List of tools provided by the MCP server.
56-
- Example configuration for agent integration.
29+
- Verified servers: All servers are versioned with full provenance and SBOM
30+
metadata
31+
- Partner tools: Servers from New Relic, Stripe, Grafana, and other trusted
32+
partners
33+
- Docker-built servers: Locally-running servers built and digitally signed by
34+
Docker for enhanced security
35+
- Remote services: Cloud-hosted servers that connect to external services like
36+
GitHub, Notion, and Linear
5737

58-
## Server deployment types
38+
You can browse the catalog at [hub.docker.com/mcp](https://hub.docker.com/mcp)
39+
or through the **Catalog** tab in Docker Desktop's MCP Toolkit.
5940

60-
The Docker MCP Catalog supports both local and remote server deployments, each optimized for different use cases and requirements.
41+
### Local versus remote servers
6142

62-
### Local MCP servers
43+
The catalog contains two types of servers based on where they run:
6344

64-
Local MCP servers are containerized applications that run directly on your machine. All local servers are built and digitally signed by Docker, providing enhanced security through verified provenance and integrity. These servers run as containers on your local environment and function without internet connectivity once downloaded. Local servers display a Docker icon {{< inline-image src="../../desktop/images/whale-x.svg" alt="docker whale icon" >}} to indicate they are built by Docker.
45+
Local servers run as containers on your machine. They work offline once
46+
downloaded and offer predictable performance and complete data privacy. Docker
47+
builds and signs all local servers in the catalog.
6548

66-
Local servers offer predictable performance, complete data privacy, and independence from external service availability. They work well for development workflows, sensitive data processing, and scenarios requiring offline functionality.
49+
Remote servers run on the provider's infrastructure and connect to external
50+
services. Many remote servers use OAuth authentication, which the MCP Toolkit
51+
handles automatically through your browser.
6752

68-
### Remote MCP servers
53+
## Using servers from the catalog
6954

70-
Remote MCP servers are hosted services that run on the provider's
71-
infrastructure and connect to external services like GitHub, Notion, and
72-
Linear. Many remote servers use OAuth authentication. When a remote server
73-
requires OAuth, the MCP Toolkit handles authentication automatically - you
74-
authorize access through your browser, and the Toolkit manages credentials
75-
securely. You don't need to manually create API tokens or configure
76-
authentication.
55+
To start using MCP servers from the catalog:
7756

78-
Remote servers display a cloud icon in the catalog. For setup instructions, see
79-
[MCP Toolkit](toolkit.md#oauth-authentication).
57+
1. Browse servers in the [MCP Catalog](https://hub.docker.com/mcp) or in Docker
58+
Desktop
59+
2. Enable servers through the MCP Toolkit
60+
3. Configure any required authentication (OAuth is handled automatically)
61+
4. Connect your AI applications to use the servers
8062

81-
## Use an MCP server from the catalog
63+
For detailed step-by-step instructions, see:
8264

83-
To use an MCP server from the catalog, see [MCP Toolkit](toolkit.md).
65+
- [Get started with MCP Toolkit](/ai/mcp-catalog-and-toolkit/get-started/) -
66+
Quick start guide
67+
- [MCP Toolkit](/ai/mcp-catalog-and-toolkit/toolkit/) - Detailed usage
68+
instructions
8469

8570
## Contribute an MCP server to the catalog
8671

@@ -95,3 +80,119 @@ within 24 hours on:
9580
- The [Docker MCP Catalog](https://hub.docker.com/mcp).
9681
- The [Docker Hub](https://hub.docker.com/u/mcp) `mcp` namespace (for MCP
9782
servers built by Docker).
83+
84+
## Custom catalogs
85+
86+
Custom catalogs let you curate focused collections of recommended servers. You
87+
can package custom server implementations alongside public servers, distribute
88+
curated lists to your team, and define what agents can discover when using
89+
Dynamic MCP.
90+
91+
Common use cases:
92+
93+
- Curate a subset of servers from the Docker MCP Catalog that your organization
94+
approves
95+
- Include community registry servers that aren't in the Docker catalog
96+
- Add your organization's private MCP servers
97+
- Control which versions of servers your team uses
98+
99+
### Custom catalogs with Dynamic MCP
100+
101+
Custom catalogs work particularly well with
102+
[Dynamic MCP](/ai/mcp-catalog-and-toolkit/dynamic-mcp/), where agents
103+
discover and add MCP servers on-demand during conversations. When you specify a
104+
custom catalog with the gateway, the `mcp-find` tool searches only within your
105+
curated catalog. If your catalog contains 20 servers instead of 300+, agents
106+
work within that focused set and can dynamically add servers as needed without
107+
manual configuration each time.
108+
109+
This gives agents the autonomy to discover and use tools while keeping their
110+
options within boundaries your team defines.
111+
112+
### Create and curate a catalog
113+
114+
The most practical way to create a custom catalog is to fork the Docker catalog
115+
and then curate which servers to keep:
116+
117+
```console
118+
$ docker mcp catalog fork docker-mcp my-catalog
119+
```
120+
121+
This creates a copy of the Docker catalog with all available servers. Export it
122+
to a file where you can edit which servers to include:
123+
124+
```console
125+
$ docker mcp catalog export my-catalog ./my-catalog.yaml
126+
```
127+
128+
Edit `my-catalog.yaml` to remove servers you don't want, keeping only the ones
129+
your team needs. Each server is listed in the `registry` section. Import the
130+
edited catalog back:
131+
132+
```console
133+
$ docker mcp catalog import ./my-catalog.yaml
134+
```
135+
136+
View your curated catalog:
137+
138+
```console
139+
$ docker mcp catalog show my-catalog
140+
```
141+
142+
#### Alternative: Build incrementally
143+
144+
You can also build a catalog from scratch. Start with an empty catalog or a
145+
template:
146+
147+
```console
148+
$ docker mcp catalog create my-catalog
149+
```
150+
151+
Or create a starter template with example servers:
152+
153+
```console
154+
$ docker mcp catalog bootstrap ./starter-catalog.yaml
155+
```
156+
157+
Add servers from other catalog files:
158+
159+
```console
160+
$ docker mcp catalog add my-catalog notion ./other-catalog.yaml
161+
```
162+
163+
### Use a custom catalog
164+
165+
Use your custom catalog when running the MCP gateway. For static server
166+
configuration, specify which servers to enable:
167+
168+
```console
169+
$ docker mcp gateway run --catalog my-catalog.yaml --servers notion,brave
170+
```
171+
172+
For Dynamic MCP, where agents discover and add servers during conversations,
173+
specify just the catalog:
174+
175+
```console
176+
$ docker mcp gateway run --catalog my-catalog.yaml
177+
```
178+
179+
Agents can then use `mcp-find` to search for servers within your catalog and
180+
`mcp-add` to enable them dynamically.
181+
182+
The `--catalog` flag points to a catalog file in `~/.docker/mcp/catalogs/`.
183+
184+
### Share your catalog
185+
186+
Share your catalog with your team by distributing the YAML file or hosting it
187+
at a URL:
188+
189+
```console
190+
$ docker mcp catalog export my-catalog ./team-catalog.yaml
191+
```
192+
193+
Team members can import it:
194+
195+
```console
196+
$ docker mcp catalog import ./team-catalog.yaml
197+
$ docker mcp catalog import https://example.com/team-catalog.yaml
198+
```

0 commit comments

Comments
 (0)