Mistral OCR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MISTRAL_API_KEY | No | Single Mistral API key (compatibility mode). | |
| MISTRAL_API_KEYS | No | Comma-, semicolon-, or newline-separated Mistral API keys for automatic fallback. | |
| MISTRAL_OCR_OUTPUT_DIR | No | Directory to save OCR Markdown outputs. Defaults to 'outputs/' next to server.py. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_api_keyC | Set one Mistral API key for this running MCP server. |
| set_api_keysC | Set one or more Mistral API keys for this running MCP server. |
| health_checkA | Check MCP configuration, key validity, output directory, and model name. |
| list_pagesB | Return basic local file information and PDF page count when available. |
| ocr_from_urlB | 从公开的文档或图片 URL 中提取 Markdown 文本。 |
| ocr_from_fileA | 从本地文件或图片中提取 Markdown 文本并以字符串形式返回。 |
| ocr_to_markdown_fileA | OCR 本地文件并将生成的 Markdown 保存至磁盘。 |
| ocr_url_to_markdown_fileA | OCR 公网 URL 指向的文件并将生成的 Markdown 保存至磁盘。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes: health_check, list_pages, and API key management are clearly separate. The four OCR tools form two pairs (from_file vs from_url, and return string vs save to file), which are distinguishable by source and output, but could cause confusion if an agent overlooks the output difference.
Naming uses a mix of patterns: 'ocr_from_file' vs 'ocr_to_markdown_file' use different prepositions for source vs destination, while 'set_api_key' and 'set_api_keys' are consistent. Overall, the names are readable but not perfectly consistent.
8 tools cover the essential functions: health check, file listing, two OCR sources, two output options, and API key management. This is well-scoped for an OCR server without being excessive.
The tool set covers all core OCR operations (from file and URL, output as string or file) plus configuration and key management. Minor gaps exist, such as no direct model selection or cache clearing, but the main workflow is complete.