Mistral OCR MCP Server

Created By
sathizz7a year ago
Mcp ocr server
Overview

what is Mistral OCR MCP Server?

Mistral OCR MCP Server is a local OCR server that utilizes Mistral OCR technology, compliant with Model Context Protocol (MCP) principles, allowing users to perform Optical Character Recognition (OCR) on uploaded images.

how to use Mistral OCR MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and run the FastAPI server. You can then upload images to the /v1/ocr endpoint for OCR processing.

key features of Mistral OCR MCP Server?

  • FastAPI backend for high performance
  • Standard OCR endpoint for image uploads
  • Configuration management using Pydantic
  • Integrated logging for monitoring
  • Health check endpoint to verify server status

use cases of Mistral OCR MCP Server?

  1. Extracting text from scanned documents
  2. Converting images of printed text into editable formats
  3. Integrating OCR capabilities into applications via MCP interface

FAQ from Mistral OCR MCP Server?

  • What types of images can be processed?

The server supports common image formats such as JPEG and PNG.

  • How do I check if the server is running?

You can use the /health endpoint to check the server status.

  • Is there a limit on the file size for uploads?

Yes, the maximum upload file size is set by default (e.g., 1MB).

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sathizz7
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago