Mistral Vibe failed a local MCP setup that Claude Code solved
On Windows, Mistral Vibe 2.18.4 with the mistral-medium-3.5 model failed for 30 minutes while trying to connect a locally cloned MCP server. The same MCP server already worked with other through . Mistral Vibe first chose the wrong HTTP setup path.
Even after receiving a Claude Code-style config string with the right transport, command, and arguments, it did not put the settings into the correct ~\.vibe\ file. It created its own mcp instead, and the setup still failed. The tool then kept trying to debug the MCP server itself, even though the server was known to work elsewhere and the real issue was Vibe’s .
Claude Code handled the same setup in 3 minutes and 37 seconds, using Context7 MCP along the way, and completed it in one try. The likely cause was a mix of weak model judgment and missing Mistral Vibe examples for locally cloned , since its examples focused on package-style names or HTTPS setups.
Key points
- Mistral Vibe 2.18.4 failed for 30 minutes on a local MCP setup on Windows.
- The same MCP server worked in other through .
- Mistral Vibe wrote settings to mcp.json instead of the expected file.
- Claude Code completed the same setup in 3 minutes and 37 seconds.
- Missing examples for locally cloned may lead an AI tool toward the wrong setup method.