Mcp Ocr

Created By
rjn32sa year ago
MCP OCR Server is a production-ready OCR solution built with Model Context Protocol (MCP), enabling seamless text extraction from images via Tesseract OCR. Supports local files, URLs, and raw bytes with multi-language capabilities and automatic setup. Fast, reliable, and easy to integrate.
Overview

what is MCP OCR?

MCP OCR is a production-grade Optical Character Recognition (OCR) server built using the Model Context Protocol (MCP) that provides OCR capabilities through a simple interface.

how to use MCP OCR?

To use MCP OCR, install it via pip, start the server, and use the provided functions to extract text from images.

key features of MCP OCR?

  • Extract text from images using Tesseract OCR
  • Support for multiple input types: local image files, image URLs, and raw image bytes
  • Automatic Tesseract installation on supported platforms
  • Support for multiple languages
  • Production-ready error handling

use cases of MCP OCR?

  1. Extracting text from scanned documents
  2. Converting images of printed text into editable formats
  3. Supporting multilingual text extraction for various applications

FAQ from MCP OCR?

  • What input types does MCP OCR support?

MCP OCR supports local image files, image URLs, and raw image bytes.

  • How do I install MCP OCR?

You can install MCP OCR using pip with the command pip install mcp-ocr.

  • Is Tesseract installed automatically?

Yes, Tesseract will be installed automatically on supported platforms like macOS, Linux, and Windows.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rjn32s
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago