Yakpdf MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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 |
|---|---|
| pdfB | Generate a PDF from a URL or HTML string. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'pdf' has a clear and distinct purpose of generating PDFs from URLs or HTML strings, leaving no room for misselection by an agent.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'pdf' is simple and descriptive, and with no other tools to compare against, there are no inconsistencies in naming patterns or conventions.
A single tool is too few for a server named 'Yakpdf MCP Server', which suggests a PDF-focused domain. While the tool covers a core function, the scope feels thin and incomplete, as typical PDF servers might include additional operations like merging, splitting, or extracting text from PDFs.
The tool surface is severely incomplete for a PDF server. It only supports generating PDFs from URLs or HTML, with no coverage for other common PDF operations such as reading, editing, converting, or managing existing PDF files. This creates significant gaps that will likely cause agent failures in broader PDF-related tasks.