mineru-docparse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINERU_API_URL | No | MinerU 服务地址 | http://localhost:8000 |
| MINERU_OUTPUT_DIR | No | 解析结果默认保存目录，设置后不用每次都指定路径 | |
| MINERU_API_TIMEOUT | No | 请求超时秒数，大文件超时可调大 | 600 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mineru_parse_documentC | 将 PDF · DOCX · PPTX · XLSX · 图片 · 网页转为结构化 Markdown / JSON 上传文件到 MinerU DocParse API 进行内容提取 |
| mineru_health_checkA | 检查 MinerU DocParse API 服务是否正常运行。 |
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 serve completely distinct purposes: one checks API health, the other parses documents. There is no overlap or ambiguity.
Both tools follow a consistent 'mineru_verb_noun' pattern using snake_case, which is clear and predictable.
Only two tools exist, which is borderline low for a typical server. However, for a focused document parsing service with a health check, it may be acceptable.
The set covers the essential operations for the server's purpose: health check and document parsing. Minor gaps like format listing or status checking are absent but workable.