From 9545c2a61133c426552c9d5b4a37cbb8da92ed53 Mon Sep 17 00:00:00 2001 From: pgflow Date: Wed, 26 Aug 2026 14:46:49 +0900 Subject: [PATCH 1/5] mcp: add Mistral Vibe to verify connections section Signed-off-by: pgflow --- .../ai/mcp-catalog-and-toolkit/get-started.md | 53 +++++++++++++++++++ 1 file changed, 53 insertions(+) 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..594036957769 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,58 @@ 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: + +```toml +[[mcp_servers]] +name = "MCP_DOCKER" +transport = "stdio" +command = ["docker"] +args = ["mcp", "gateway", "run", "--profile", "my_profile"] +startup_timeout_sec = 60 +disabled = false +``` + +> [!NOTE] +> 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 +> ``` + +Restart Vibe and check the MCP server status. Vibe logs MCP connection +results at startup. Check the log for a successful connection: + +```console +$ grep "MCP" ~/.vibe/logs/vibe.log | tail -5 +``` + +If the connection fails, the log shows the error: + +```console +$ grep "MCP stdio discovery failed" ~/.vibe/logs/vibe.log +``` + +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) From a927a39b3705a08a96635618d9e68c653db50b3e Mon Sep 17 00:00:00 2001 From: pgflow Date: Wed, 26 Aug 2026 15:14:48 +0900 Subject: [PATCH 2/5] mcp: refine Mistral Vibe verify connections section Signed-off-by: pgflow --- .../ai/mcp-catalog-and-toolkit/get-started.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) 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 594036957769..3bcc4a3f4520 100644 --- a/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md +++ b/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md @@ -396,6 +396,10 @@ startup_timeout_sec = 60 disabled = false ``` +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. + > [!NOTE] > On Windows, the Docker installation path (`C:\Program Files\Docker\...`) > contains a space. Use a list for `command` with the full path to @@ -413,19 +417,17 @@ disabled = false > disabled = false > ``` -Restart Vibe and check the MCP server status. Vibe logs MCP connection -results at startup. Check the log for a successful connection: - -```console -$ grep "MCP" ~/.vibe/logs/vibe.log | tail -5 -``` - -If the connection fails, the log shows the error: +Restart Vibe. If the connection is successful, Vibe exposes MCP tools prefixed +with `MCP_DOCKER_` (such as `MCP_DOCKER_fetch`, `MCP_DOCKER_search`, and so on). +To verify, check that no `MCP stdio discovery failed` warnings appear in the +log: ```console $ grep "MCP stdio discovery failed" ~/.vibe/logs/vibe.log ``` +If the command returns no output, the connection is successful. + Test the connection by submitting a prompt that invokes one of your installed MCP servers: From 95e1add336066e94b536611ebdf63b16bfd0e5a1 Mon Sep 17 00:00:00 2001 From: pgflow Date: Wed, 26 Aug 2026 16:18:34 +0900 Subject: [PATCH 3/5] mcp: use tabs and /mcp command for Mistral Vibe section Signed-off-by: pgflow --- .../ai/mcp-catalog-and-toolkit/get-started.md | 53 ++++++++++--------- 1 file changed, 29 insertions(+), 24 deletions(-) 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 3bcc4a3f4520..3e1e9bde194b 100644 --- a/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md +++ b/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md @@ -386,6 +386,9 @@ MCP servers: 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="macOS / Linux" >}} + ```toml [[mcp_servers]] name = "MCP_DOCKER" @@ -396,38 +399,40 @@ 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. -> [!NOTE] -> 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 -> ``` - -Restart Vibe. If the connection is successful, Vibe exposes MCP tools prefixed -with `MCP_DOCKER_` (such as `MCP_DOCKER_fetch`, `MCP_DOCKER_search`, and so on). -To verify, check that no `MCP stdio discovery failed` warnings appear in the -log: +Restart Vibe and run the `/mcp` command in a Vibe CLI session. The +`MCP_DOCKER` server should appear with its tools listed: ```console -$ grep "MCP stdio discovery failed" ~/.vibe/logs/vibe.log +$ vibe +> /mcp ``` -If the command returns no output, the connection is successful. - Test the connection by submitting a prompt that invokes one of your installed MCP servers: From 7d43934dd1a89e4d2d5d451587e8b8e0c4e518e4 Mon Sep 17 00:00:00 2001 From: pgflow Date: Wed, 26 Aug 2026 16:28:36 +0900 Subject: [PATCH 4/5] mcp: split macOS/Linux tab into separate Linux and macOS tabs Signed-off-by: pgflow --- .../ai/mcp-catalog-and-toolkit/get-started.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) 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 3e1e9bde194b..7baade266f4d 100644 --- a/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md +++ b/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md @@ -387,7 +387,20 @@ 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="macOS / Linux" >}} +{{< 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]] From af2d8dfee5f931b774e3bf7e332217e039fa3e5d Mon Sep 17 00:00:00 2001 From: pgflow Date: Wed, 26 Aug 2026 16:43:28 +0900 Subject: [PATCH 5/5] mcp: refine /mcp command description for Mistral Vibe Signed-off-by: pgflow --- content/manuals/ai/mcp-catalog-and-toolkit/get-started.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 7baade266f4d..69c4af74f8be 100644 --- a/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md +++ b/content/manuals/ai/mcp-catalog-and-toolkit/get-started.md @@ -438,8 +438,8 @@ 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 and run the `/mcp` command in a Vibe CLI session. The -`MCP_DOCKER` server should appear with its tools listed: +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