Mistral MCP vs Server Everything
A side-by-side look at the Mistral MCP and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mistral MCP for other tools and integrations work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mistral MCP when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MISTRAL_API_KEY. - You want tools like
mistral_chat, codestral_fim, mistral_vision.
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
echo, get-annotated-message, get-env.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 65/100 · Great | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | MISTRAL_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 15 | 91,525 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 8 | 16 |
| Full listing | View Mistral MCP | View Server Everything |
Tools & capabilities
Mistral MCP tools 8
mistral_chatGenerate a chat completion using a Mistral model. When to use: - Drafting French (or any European-language) content where Mistral shines. - Codestral for code-specific generation/review. - Ministral for cheap / low-latency classification. Returns structured content with the assistant text and token usage. Does NOT stream — use mistral_chat_stream for long outputs with progress updates.codestral_fimFill-in-the-middle code completion with Codestral. Given `prompt` (code preceding the cursor) and `suffix` (code after the cursor), Codestral writes the middle. Use for editor autocomplete scenarios, code-patching agents, or structured refactors where you know the target boundaries. Default stop tokens: [] — let the model decide. Override with `stop` if needed.mistral_visionChat completion with multimodal input: text + image_url parts. Requires a vision-capable model. Accepted: - pixtral-large-latest - pixtral-12b-latest - mistral-large-latest - mistral-medium-latest - mistral-small-latest Each message's `content` is either a plain string (pure text) or an array of parts `{ type: 'text', text }` / `{ type: 'image_url', imageUrl }`. The image URL can be an https URL or a data: URI base64 payload. Returns the assistant text + token usage. For non-visual requests, prefer `mistral_chat`.mistral_ocrRun Mistral OCR on a PDF or image, returning structured markdown per page. Input `document` is one of: - { type: "document_url", documentUrl: "https://...pdf" } - { type: "image_url", imageUrl: "https://..." | "data:image/..." } - { type: "file", fileId: "<id-from-files-api>" } Options: - `pages`: array of 0-indexed page numbers or string like "0-5,7". - `tableFormat`: 'markdown' (default) or 'html'. - `extractHeader` / `extractFooter`: include page header/footer when present. - `includeImageBase64`: embed extracted image bytes as base64 in the response. - `document_annotation_format`: JSON schema for whole-document structured extraction. - `bbox_annotation_format`: JSON schema for extracted image / bbox annotations. - `confidence_scores_granularity`: 'page' or 'word'. Returns `pages[].markdown` plus optional `pages[].hyperlinks`, `header`, `footer`, `images` bounding boxes, annotations, confidence scores, and `dimensions`.voxtral_transcribeTranscribe an audio file to text using Mistral Voxtral. Accepted models: - voxtral-mini-latest - voxtral-small-latest Audio source is one of: - { type: "file_url", fileUrl: "https://..." } (public URL) - { type: "file", fileId: "<id-from-files-api>" } Options: - `language`: ISO-639-1 hint (e.g. 'fr', 'en'). Boosts accuracy when known. - `temperature`: sampling temperature. - `diarize`: return per-speaker segments (default false). - `timestampGranularities`: ['segment'] to return per-segment timestamps. - `contextBias`: list of phrases/terms that should bias the decoder. Returns plain `text`, detected `language`, optional `segments[]`, and token usage.workflow_executeStart a Mistral Workflow execution. `workflowIdentifier` is the workflow name or ID (visible in mistral://workflows). `input` is a free-form JSON object matching the workflow's input schema. Modes: - waitForResult=false (default): returns immediately with execution_id and RUNNING status. Poll workflow_status to track completion. - waitForResult=true: blocks until the workflow finishes and returns the result inline. Use timeoutSeconds (default 30) to cap the wait. Use deploymentName to target a specific deployment slot when multiple are configured.workflow_statusGet the current state and result of a workflow execution. Statuses: RUNNING | COMPLETED | FAILED | CANCELED | TERMINATED | CONTINUED_AS_NEW | TIMED_OUT | RETRYING_AFTER_ERROR Poll until status is COMPLETED (or terminal) when waitForResult was false. `result` is populated once the workflow reaches a terminal state.workflow_interactSend a signal to or run a query against a running workflow execution. action=signal: fire-and-forget event; the workflow reacts asynchronously. - `name`: signal name defined in the workflow. - `input`: optional payload matching the signal's schema. action=query: synchronous read of internal workflow state. - `name`: query handler name defined in the workflow. - `input`: optional parameters for the query. - Returns `query_name` + `result` inline. action=update: synchronous request to modify workflow state mid-execution. - `name`: update handler name defined in the workflow. - `input`: optional payload for the update. - Returns `update_name` + `result` inline.
Server Everything tools 16
echoEchoes back the input stringget-annotated-messageDemonstrates how annotations can be used to provide metadata about content.get-envReturns all environment variables, helpful for debugging MCP server configurationget-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.get-resource-linksReturns up to ten resource links that reference different types of resourcesget-resource-referenceReturns a resource reference that can be used by MCP clientsget-structured-contentReturns structured content along with an output schema for client data validationget-sumReturns the sum of two numbersget-tiny-imageReturns a tiny MCP logo image.gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mistral MCP
{
"mcpServers": {
"swih-mistral-mcp": {
"command": "npx",
"args": [
"-y",
"mistral-mcp@1.0.0"
],
"env": {
"MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE"
}
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Mistral MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Mistral MCP for other tools and integrations work and Server Everything for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mistral MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Server Everything is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add swih-mistral-mcp and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mistral MCP has a quality signal of 65/100 (Great) with 2 views, 0 installs and 15 GitHub stars. Server Everything has 73/100 (Great) with 9 views, 0 installs and 91,525 GitHub stars.