pdf-mcp
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pdf_infoB | Get metadata and basic info about a PDF file. |
| get_table_of_contentsA | Get the table of contents (bookmarks/outline) from a PDF. |
| get_page_textA | Extract text content from one or more PDF pages. |
| get_page_imageA | Render a single PDF page as a PNG image. |
| search_textA | Search for text in a PDF file (case-insensitive). |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: get_page_image renders visual content, get_page_text extracts textual content, get_pdf_info provides metadata, get_table_of_contents retrieves structural outline, and search_text performs text search. The descriptions reinforce these distinct functions, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes (get_page_image, get_page_text, get_pdf_info, get_table_of_contents, search_text). The naming convention is perfectly uniform across all five tools, using snake_case throughout without any deviations.
Five tools is well-scoped for a PDF processing server, covering core operations without bloat. Each tool serves a specific, essential function (rendering, text extraction, metadata, navigation, and search), making the count appropriate and efficient for the domain.
The toolset covers most fundamental PDF operations well, including reading, extracting, navigating, and searching. A minor gap exists in write/modify operations (e.g., merging, splitting, or annotating PDFs), but the provided tools are sufficient for common agent workflows involving PDF analysis and content retrieval.