MCP

The Mistral MCP server connects an AI agent to your Studio workspace over the Model Context Protocol. It exposes your workspace as MCP tools and authenticates each request with your Mistral API key.

Use it from wherever your agent runs: a coding CLI, an IDE, a desktop assistant, or your own application.


Endpoint	`https://api.mistral.ai/mcp`
Transport	Streamable HTTP
Authentication	`Authorization: Bearer <MISTRAL_API_KEY>`

Before you begin

A Mistral API key. Keys are workspace-scoped, so the agent gets the access that key already has.
An MCP client that supports the streamable HTTP transport and static request headers.

Export the key in the environment that launches your client:

export MISTRAL_API_KEY="your_api_key"

export MISTRAL_API_KEY="your_api_key"

Connect a client

vibe mcp add mistralai \
  --url https://api.mistral.ai/mcp \
  --transport streamable-http \
  --api-key-env MISTRAL_API_KEY

vibe mcp add mistralai \
  --url https://api.mistral.ai/mcp \
  --transport streamable-http \
  --api-key-env MISTRAL_API_KEY

This writes the entry to ~/.vibe/config.toml:

[[mcp_servers]]
name = "mistralai"
transport = "streamable-http"
url = "https://api.mistral.ai/mcp"

[mcp_servers.auth]
type = "static"
api_key_env = "MISTRAL_API_KEY"

[[mcp_servers]]
name = "mistralai"
transport = "streamable-http"
url = "https://api.mistral.ai/mcp"

[mcp_servers.auth]
type = "static"
api_key_env = "MISTRAL_API_KEY"

The configuration stores the variable name and the environment holds the key. Run /mcp mistralai in a session to list the tools. See MCP servers for permissions and tool filtering.

What the server exposes

Skills, the reusable instruction sets you manage in Studio›Skills ↗. An agent browses the workspace catalog, reads a Skill and the files shipped with it, creates a new Skill version, changes who it is shared with, or deletes it. A Skill written from your editor appears in Studio, and a Skill written in Studio is available to the agent.

Skills is the first capability, and more follow. The server lists the tools available to your key, so ask your client for its tool list, or call tools/list. Each tool describes its own arguments.

Access and permissions

Every call uses your API key's permissions.

Some tools write: they add Skill versions, change sharing, and delete Skills. Configure per-tool approval in your client to review those calls before they run.

Troubleshooting

Problem	Cause	Solution
`401 {"detail":"Invalid API Key"}`	The key is missing, misspelled, or revoked.	Export the variable in the environment that launches your client, and check the key is active in the console.
A tool call returns a permission error.	The operation requires additional workspace access.	Ask a workspace admin for the matching access, then retry.

Next steps

Create a Skill in Studio to give the agent something to work with.
MCP servers in the Vibe Code CLI for per-tool permissions and filtering.
API keys to create and rotate the key you connect with.