MCP-MinerU
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| parse_pdfA | Parse PDF and image files (PDF, JPEG, PNG, etc.) to extract text, tables, formulas, and structure using MinerU vunknown. Supports multiple backends including MLX-accelerated inference on Apple Silicon. Works with documents, screenshots, photos, and scanned images. |
| list_backendsB | Check system capabilities and list recommended backends for document and image parsing |
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
parse_pdf and list_backends have completely distinct purposes: one performs the actual document/image parsing, while the other reports system capabilities. No overlap or ambiguity exists between them.
Both tool names follow a consistent verb_noun pattern in snake_case (parse_pdf, list_backends). The naming is predictable and uniform across the set.
With only two tools, the server feels minimal for its stated purpose of document and image parsing. While the scope is narrow, a slightly more complete set (e.g., separate format detection or result retrieval) might be expected in a fuller-featured server.
For the domain of document parsing, parse_pdf covers the core extraction of text, tables, formulas, and structure across multiple file types, while list_backends addresses capability discovery. There are no obvious dead ends or missing critical operations within this focused scope.