mcp_ocr
Related Servers
Alternatives to mcp_ocr
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceModular OCR MCP server with pluggable backends (Apple Vision, PaddleOCR, PaddleOCR-VL) for extracting text, tables, formulas, and charts from images.-
- AlicenseCqualityDmaintenanceA local OCR MCP server that extracts text from images using PP-OCRv6 for fast text extraction and VL-1.6 for document structure analysis, with automatic model routing and GPU detection.32MIT
- FlicenseNot gradedqualityDmaintenanceProvides OCR (Optical Character Recognition) capabilities through MCP, including text extraction and document layout parsing to Markdown. Supports multiple PaddleOCR models like PP-OCRv5, PP-OCRv6, and PP-StructureV3.-
- AlicenseNot gradedqualityNot gradedmaintenanceA macOS-based MCP server that enables high-accuracy text extraction from PDF and image files using the OwlOCR app or Apple's Vision Framework. It supports multi-language OCR and provides asynchronous tools for processing documents directly within MCP clients.MIT
- AlicenseBqualityBmaintenanceOpen-source MCP vision server that gives text-only LLMs and AI agents image understanding: OCR, visual inspection, annotation reading, UI layout analysis, screenshot-to-code reconstruction, and image comparison, with Ollama, OpenAI-compatible, Anthropic, or Gemini backends.61MIT
- AlicenseAqualityDmaintenanceMCP server for image recognition, supporting multiple vision backends (Anthropic, Zhipu, Ollama) to describe, answer questions, and analyze images.355 npm1MIT
TDQS
Scored across 15 tools
Names encode both capability and backend (ocr_{capability}_{backend}), so an agent can distinguish 'table' from 'layout' from 'text' tasks and see the backend choice explicitly. The main ambiguity is intentional duplication: ocr_text_vision, ocr_text_paddle and ocr_text_xiaomi do the same job, and choosing between them requires reading descriptions (speed vs language vs installation). Within the xiaomi family, ocr_layout_xiaomi, ocr_document_xiaomi and ocr_kie_xiaomi overlap in structured-output scope, though the descriptions do draw the lines.
A strict, predictable ocr_<capability>_<backend> pattern consistently applied across all 15 tools, with occasional longer capability names (document, formula, kie) that still read naturally. No mixing of camelCase, no stray verb styles, and the backend suffix lets an agent infer an entire tool family from one name.
15 tools is near the top of a comfortable range, but the count is explained by a sensible capability × backend matrix rather than ad-hoc sprawl. It is slightly heavy because each capability is triplicated across three backends, which could have been a single backend parameter; still, each tool corresponds to a real, distinct invocation.
Covers the core OCR surface well: plain text, layout blocks, tables, formulas, full-document Markdown, key-information extraction, and batch processing across three backends. Gaps are minor but notable: no capability/backend discovery tool (an agent cannot check which backends are installed or supported), and features like formula/document/KIE exist only under the xiaomi backend, so workflow coverage is uneven across backends.