diff --git a/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md b/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md
index 4c2f8e8e6913..69c4af74f8be 100644
--- a/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md
+++ b/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md
@@ -130,6 +130,7 @@ is working:
 - [Sema4.ai](#sema4)
 - [Visual Studio Code](#vscode)
 - [Zed](#zed)
+- [Mistral Vibe](#mistral-vibe)
 
 ### Claude Code
 
@@ -380,6 +381,78 @@ MCP servers:
 {{% param test_prompt %}}
 ```
 
+### Mistral Vibe
+
+Mistral Vibe uses a TOML configuration file at `~/.vibe/config.toml`. Add the
+MCP Toolkit as a stdio MCP server in the `[[mcp_servers]]` section:
+
+{{< tabs >}}
+{{< tab name="Linux" >}}
+
+```toml
+[[mcp_servers]]
+name = "MCP_DOCKER"
+transport = "stdio"
+command = ["docker"]
+args = ["mcp", "gateway", "run", "--profile", "my_profile"]
+startup_timeout_sec = 60
+disabled = false
+```
+
+{{< /tab >}}
+{{< tab name="macOS" >}}
+
+```toml
+[[mcp_servers]]
+name = "MCP_DOCKER"
+transport = "stdio"
+command = ["docker"]
+args = ["mcp", "gateway", "run", "--profile", "my_profile"]
+startup_timeout_sec = 60
+disabled = false
+```
+
+{{< /tab >}}
+{{< tab name="Windows" >}}
+
+On Windows, the Docker installation path (`C:\Program Files\Docker\...`)
+contains a space. Use a list for `command` with the full path to `docker.exe`,
+and add `PROGRAMFILES` and `PROGRAMDATA` environment variables that the MCP
+Python SDK doesn't inherit by default:
+
+```toml
+[[mcp_servers]]
+name = "MCP_DOCKER"
+transport = "stdio"
+command = ["C:/Program Files/Docker/Docker/resources/bin/docker.exe"]
+args = ["mcp", "gateway", "run", "--profile", "my_profile"]
+env = { PROGRAMFILES = "C:\\Program Files", PROGRAMDATA = "C:\\ProgramData" }
+startup_timeout_sec = 60
+disabled = false
+```
+
+{{< /tab >}}
+{{< /tabs >}}
+
+The `startup_timeout_sec = 60` is recommended because the Docker MCP Gateway
+takes approximately 15-25 seconds to start. The default timeout is 10 seconds,
+which isn't enough for the gateway to initialize.
+
+Restart Vibe. In a Vibe CLI session, run `/mcp` to view active MCP servers.
+The `MCP_DOCKER` server should appear in the list:
+
+```console
+$ vibe
+> /mcp
+```
+
+Test the connection by submitting a prompt that invokes one of your installed
+MCP servers:
+
+```console
+$ vibe "{{% param test_prompt %}}"
+```
+
 ## Further reading
 
 - [MCP Profiles](/manuals/ai/mcp-catalog-and-toolkit/profiles.md)