MCP PDF Extract
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDF_DIR | No | Directory containing PDF files (default: ./data/pdfs) | |
| MAX_PDF_SIZE_KB | No | Maximum allowed PDF file size in KB (default: 350) |
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 |
|---|---|
| read_doc_contentsA | Read the contents of a PDF document and return it as a string. |
| list_available_pdfsB | List all available PDF documents that can be read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists available PDFs, the other reads their contents. There is no overlap or ambiguity.
Both tools use snake_case and follow a verb_noun pattern (read_doc_contents, list_available_pdfs). The slight inconsistency between 'doc_contents' and 'pdfs' is minor, and overall naming is predictable.
With only 2 tools, the server is minimal. For a PDF extraction server, a few more tools (e.g., extract metadata, search text) would be expected, but the scope may be intentionally narrow.
The server lacks common operations like extracting specific pages, retrieving metadata, or searching within PDFs. The surface is incomplete for typical PDF extraction tasks.