GLM OCR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZHIPU_API_KEY | Yes | API key for ZhipuAI GLM-OCR services |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_textB | Extract text from local files or URLs. Supported formats: PNG, JPG/JPEG, PDF. |
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
Only one tool exists, so there is no possibility of confusing it with another. Its purpose is clearly described as extracting text from files or URLs.
The single tool name 'extract_text' follows a clear verb_noun pattern. With only one tool, there are no inconsistencies to assess.
A single tool serves a narrow OCR purpose, but by the rubric 1-2 tools feels thin. It is functional but borderline for a full MCP server.
The tool covers the core OCR workflow for common formats (PNG, JPG, PDF) from both local files and URLs. It lacks advanced features like batch processing or layout detection, but these are not essential for basic text extraction.