mcp-pdf-reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | Your PyPI token for publishing | |
| UV_PUBLISH_PASSWORD | No | Your PyPI password for publishing | |
| UV_PUBLISH_USERNAME | No | Your PyPI username for publishing |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open-pdfC | Open a PDF file |
| close-pdfC | Close an open PDF file |
| list-pdf-metadataC | List metadata of an open PDF |
| get-pdf-page-countC | Get the page count of a PDF |
| get-pdf-page-textC | Get the text content of a specific page in a PDF |
| pdf-to-textC | Extract all text from a PDF document |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-pdf | Creates a summary of a PDF document |
| extract-text-from-pdf | Extract text from a specific page or range of a PDF |
| analyze-pdf | Analyze a PDF and answer questions about its content |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting different PDF operations: opening/closing files, retrieving metadata, page-specific text, full text extraction, and page counting. There is no overlap in functionality that would cause agent confusion.
The naming follows a consistent pattern with hyphen-separated descriptive names (e.g., open-pdf, get-pdf-page-text), but there is a minor deviation with 'pdf-to-text' which uses 'to' instead of a verb like 'extract'. Overall, the pattern is highly readable and predictable.
With 6 tools, this server is well-scoped for PDF reading operations. Each tool serves a specific, essential function (open, close, metadata, page count, page text, full text), and there are no extraneous or missing tools for the domain.
The toolset provides complete coverage for PDF reading: open/close lifecycle, metadata access, page-level and full-text extraction, and page counting. There are no obvious gaps; agents can perform all core PDF reading tasks without dead ends.