diff --git a/content/manuals/ai/mcp-catalog-and-toolkit/cli.md b/content/manuals/ai/mcp-catalog-and-toolkit/cli.md index d4bbcb6871..fd7a6db79a 100644 --- a/content/manuals/ai/mcp-catalog-and-toolkit/cli.md +++ b/content/manuals/ai/mcp-catalog-and-toolkit/cli.md @@ -1,7 +1,7 @@ --- title: Use MCP Toolkit from the CLI linkTitle: Use with CLI -description: Manage MCP profiles, servers, and catalogs using the Docker MCP CLI. +description: Manage MCP profiles, servers, and catalogs using Docker MCP CLI. keywords: docker mcp, cli, profiles, servers, catalog, gateway weight: 35 --- @@ -73,12 +73,12 @@ select a server, and check the **Server ID** field. Servers are referenced by URI. The URI format depends on where the server comes from: -| Format | Source | -| --- | --- | -| `catalog:///` | An OCI catalog | -| `docker://:` | A Docker image | -| `https:///v0/servers/` | The MCP community registry | -| `file://` | A local YAML or JSON file | +| Format | Source | +| ------------------------------------- | -------------------------- | +| `catalog:///` | An OCI catalog | +| `docker://:` | A Docker image | +| `https:///v0/servers/` | The MCP community registry | +| `file://` | A local YAML or JSON file | The most common format is `catalog://`, where `` matches the **Catalog** field and `` matches the **Server ID** field shown in @@ -222,39 +222,53 @@ $ echo ".vscode/mcp.json" >> .gitignore ## Share profiles +Share profiles with your team using OCI registries or version control. + +### Share via OCI registry + Profiles are shared as OCI artifacts via any OCI-compatible registry. Credentials are not included for security reasons. Team members configure -OAuth separately after pulling. +authentication credentials separately after pulling. -### Push a profile - -```console -$ docker mcp profile push -``` - -For example: +To push an existing profile called `web-dev` to an OCI registry: ```console $ docker mcp profile push web-dev registry.example.com/profiles/web-dev:v1 ``` -### Pull a profile - -```console -$ docker mcp profile pull -``` - -For example: +To pull the same profile: ```console $ docker mcp profile pull registry.example.com/profiles/team-standard:latest ``` +### Share via version control + +For project-specific profiles, you can use the `export` and `import` commands +and store the profiles in version control alongside your code. Team members can +import the file to get the same configuration. + +To export a profile to your project directory: + +```console +$ mkdir -p .docker +$ docker mcp profile export web-dev .docker/mcp-profile.json +``` + +Team members who clone the repository can import the profile: + +```console +$ docker mcp profile import .docker/mcp-profile.json +``` + +This creates a profile with the servers and configuration defined in the +file. Any authentication credentials must be configured separately if needed. + ## Custom catalogs -Custom catalogs let you curate a focused collection of servers for your team or -organization. For an overview of what custom catalogs are and when to use them, -see [Custom catalogs](/manuals/ai/mcp-catalog-and-toolkit/catalog.md#custom-catalogs). +Custom catalogs let you curate a focused collection of servers for your team +or organization. For an overview of what custom catalogs are and when to use +them, see [Custom catalogs](/manuals/ai/mcp-catalog-and-toolkit/catalog.md#custom-catalogs). Catalogs are referenced by OCI reference, for example `registry.example.com/mcp/my-catalog:latest`. Servers within a catalog use @@ -267,7 +281,8 @@ Use the Docker catalog as a base, then add or remove servers to fit your organization's needs. Copy it first: ```console -$ docker mcp catalog tag mcp/docker-mcp-catalog registry.example.com/mcp/company-tools:latest +$ docker mcp catalog tag mcp/docker-mcp-catalog \ + registry.example.com/mcp/company-tools:latest ``` List the servers it contains: @@ -279,7 +294,8 @@ $ docker mcp catalog server ls registry.example.com/mcp/company-tools:latest Remove servers your organization doesn't approve: ```console -$ docker mcp catalog server remove registry.example.com/mcp/company-tools:latest \ +$ docker mcp catalog server remove \ + registry.example.com/mcp/company-tools:latest \ --name ``` @@ -357,7 +373,8 @@ can find to your curated set. To enable specific servers from your catalog without using a profile: ```console -$ docker mcp gateway run --catalog --servers --servers +$ docker mcp gateway run --catalog \ + --servers --servers ``` ## Further reading diff --git a/content/manuals/ai/mcp-catalog-and-toolkit/profiles.md b/content/manuals/ai/mcp-catalog-and-toolkit/profiles.md index 9231489d9b..8da3d6601e 100644 --- a/content/manuals/ai/mcp-catalog-and-toolkit/profiles.md +++ b/content/manuals/ai/mcp-catalog-and-toolkit/profiles.md @@ -6,12 +6,13 @@ keywords: Docker MCP, profiles, MCP servers, configuration, sharing weight: 25 --- -{{< summary-bar feature_name="Docker MCP Toolkit" >}} +{{< summary-bar feature_name="MCP Profiles" >}} -> [!NOTE] -> This page describes the MCP Toolkit interface in Docker Desktop 4.62 and -> later. Earlier versions have a different UI. Upgrade to follow these -> instructions exactly. +> [!IMPORTANT] +> MCP Profiles is rolling out gradually in Docker Desktop 4.63. If you don't +> see the **Profiles** tab in your Docker Desktop, it hasn't been enabled for +> your account yet. It will become available to all users as the rollout +> completes. Profiles organize your MCP servers into named collections. Without profiles, you'd configure servers separately for every AI application you use. Each time diff --git a/data/summary.yaml b/data/summary.yaml index d185551d56..89d2f36c76 100644 --- a/data/summary.yaml +++ b/data/summary.yaml @@ -184,6 +184,9 @@ Docker MCP Catalog: availability: Beta Docker MCP Toolkit: availability: Beta +MCP Profiles: + availability: Early Access + requires: Docker Desktop 4.63 and later Docker Pass: requires: Docker Desktop 4.54 and later availability: Beta