space-ocr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPACE_OCR_API_KEY | Yes | Your API key for space-ocr.com |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ocr_extractA | Extract structured data from a document image (receipt, invoice, ID, etc.) using space-ocr. Returns JSON with extracted fields plus verified per-character bounding boxes (re-anchored to Vision API symbols, not LLM-hallucinated). Provide either |
| list_templatesA | List all built-in document templates supported by space-ocr. Use the returned |
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 2 tools
The two tools have completely distinct purposes: one extracts data from images, the other lists available templates. There is no overlap or ambiguity between them.
Both tools use snake_case and follow a verb_noun pattern (ocr_extract, list_templates). However, 'ocr_extract' is slightly redundant since the server name already includes OCR, but it's still clear.
Only 2 tools for an OCR server is minimal but acceptable given the focused scope on extracting structured data using built-in templates. Could benefit from additional management tools.
The set covers listing templates and extracting data, which are the core operations. Missing functionality like template management or field validation is minor given the server's narrow purpose.