mcp-dharmamitra
Related Servers
Alternatives to mcp-dharmamitra
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables local OCR transcription of images using tesseract.js, with optional low-token AI-generated descriptions, folder batch processing, and compatibility with MCP clients like ChatGPT, Claude, opencode, and Cursor.40MIT
- AlicenseNot gradedqualityCmaintenanceEnables OCR-based text, table, handwriting, and formula recognition from images via MCP, supporting local files and URLs for integration with AI assistants.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants and applications to perform optical character recognition (OCR) from images via stdin/stdout streams or REST API endpoints.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to perform local OCR on image files or base64-encoded images, returning recognized text with optional bounding boxes and confidence scores.1Apache 2.0
- AlicenseAqualityAmaintenanceEnables converting images (JPEG, PNG, GIF, WebP) into text descriptions using OpenAI-compatible vision models, with support for both local files and URLs.216MIT
- FlicenseAqualityDmaintenanceA Tesseract.js-based server that enables image-to-text recognition within MCP-compatible environments like Cursor. It supports multiple languages and common image formats, allowing users to extract text from local files using natural language commands.2-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one; its purpose (OCR an image and write text to a file) is unambiguous. An agent cannot confuse it with anything else in this server.
The single tool uses a clean, predictable verb_noun-style name (ocr_image) with snake_case arguments that match the naming convention. No competing conventions exist to create inconsistency.
One tool is thin for a named service like Dharmamitra, which suggests an OCR/document-processing domain that could span submission, status, and result retrieval. The tool does bundle the full submit-and-poll workflow, so it is self-contained, but the surface is minimal.
The core OCR operation, polling, and file output are covered, but there is no batch processing, no job status/list/cancel operation, and no way to discover supported models or endpoints. These are workable gaps but leave the lifecycle incomplete.