optical-read-mcp
Related Servers
Alternatives to optical-read-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that enables LLMs to understand images without native vision by converting image regions into text encodings (ASCII art, grayscale grids, color stats) and supporting progressive zoom, OCR, and overview summaries. Users can load images, get chunk overviews, crop and encode specific regions, and extract text using normalized coordinates.-
- AlicenseAqualityBmaintenanceMCP server that analyzes images, reads code and ZIP archives, and provides text context for non-vision models.37 npm2MIT
- AlicenseAqualityAmaintenanceMCP server that provides vision capabilities to coding agents, enabling them to analyze screenshots, UI mockups, terminal errors, documents, tables, and charts through OpenAI-compatible vision models. Supports local stdio and remote HTTP deployments with structured JSON output and binary upload side channels.820 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables text-only models to understand images through a conversational MCP server, supporting multi-turn follow-ups, URL inputs, and OpenAI-compatible vision APIs.1MIT
- AlicenseBqualityAmaintenanceA local MCP server that ingests entire repositories into a large context window (GLM-5.2 1M tokens) for coding agents, bypassing file limits and reducing query costs.31MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: ReadMassive reads files, ReadMassiveText renders arbitrary text, and ReadMassiveEstimate provides cost/compression estimates. Despite the shared ReadMassive prefix, the descriptions clearly separate file-based, text-based, and estimation workflows, leaving no ambiguity.
All tool names share the consistent 'ReadMassive' prefix with descriptive suffixes, forming a predictable pattern. The camelCase style is uniform and clearly conveys the tool's role (read, text, estimate).
Three tools is an ideal scope for a focused optical-reading server: one for file reading, one for in-memory text, and one for cost estimation. Each tool earns its place, and the count is neither too thin nor excessive.
The core reading workflow is well covered (files, text, and estimation for files). A minor gap is that ReadMassiveEstimate only accepts paths, not arbitrary text, so users cannot estimate costs for non-file content before using ReadMassiveText. Overall, the surface is nearly complete for its stated purpose.