mcp-dharmamitra
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DHARMAMITRA_COOKIE | No | Optional Cloudflare cf_clearance cookie value. Most requests go through without any cookie; if you get a 403, grab a fresh cf_clearance value from a logged-in browser session on dharmamitra.org and set it. The server will attach it as a cookie on every request. Do not hardcode it — Cloudflare rotates the value. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ocr_imageA | Run Dharmamitra OCR on an image and save extracted text to a file. Args: image_path: Absolute path to a local image file (png/jpg/…). output_path: File path where the extracted text will be written (UTF-8). transliterate_devanagari_to_iast: Pass-through flag for the API. transliterate_tibetan_to_wylie: Pass-through flag for the API. instruction: Optional instruction string for the OCR model. model: OCR model id ("auto" by default). poll_interval_seconds: Delay between status polls. timeout_seconds: Overall polling timeout. Returns a summary with job_id, output_path, pages, processing time and char count. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.