@anvme/mistral-mcp
v1.0.2
Published
MCP server wrapping Mistral Vibe CLI — use Mistral as a second opinion or coding agent in Claude Code, Cursor, Zed, and any MCP client
Maintainers
Readme
@anvme/mistral-mcp
MCP server wrapping Mistral Vibe CLI — use Mistral as a second opinion or coding agent inside Claude Code, Cursor, Zed, and any MCP client.
Requirements
Install and configure Mistral Vibe CLI:
curl -LsSf https://mistral.ai/vibe/install.sh | bash
vibe --setup # enter your Mistral API key onceTools
| Tool | Description | Default model |
|------|-------------|---------------|
| ask_mistral | Ask Mistral a question — second opinion on code, architecture, debugging | vibe default (devstral-2) |
| vibe_task | Give Vibe a coding task in a project directory (reads/writes files, runs bash) | vibe default (devstral-2) |
Claude Code setup
Add to ~/.claude.json mcpServers — no API key needed, stored by vibe --setup:
"mistral": {
"command": "npx",
"args": ["-y", "@anvme/mistral-mcp"]
}Optional: switch ask_mistral to Mistral Large
mistral-large-latest is better for general Q&A and architecture questions. To enable it:
1. Add the model to ~/.vibe/config.toml:
[[models]]
name = "mistral-large-latest"
provider = "mistral"
alias = "mistral-large-latest"
temperature = 0.2
input_price = 0.5
output_price = 1.5
thinking = "off"
auto_compact_threshold = 2000002. Create the agent at ~/.vibe/agents/mistral-large.toml:
active_model = "mistral-large-latest"3. Restart Claude Code — ask_mistral will now use Mistral Large automatically.
