pdfdancer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DCS_BASE_URL | No | The URL pointing at the running Cloudflare Worker or local dev server. Also accepts DOCUSAURUS_SEARCH_BASE_URL. | http://localhost:8787 |
| DOCUSAURUS_SEARCH_BASE_URL | No | Alternative environment variable for the Cloudflare Worker or local dev server URL. | http://localhost:8787 |
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 |
|---|---|
| helpB | Explains the purpose of this server and how to use it. |
| versionA | Returns the current version of the pdfdancer-mcp server. |
| search-docsA | Search the official PDFDancer SDK documentation by keyword. Returns matching documentation routes with titles, content snippets, and relevance scores. Use this to find information about PDFDancer features, APIs, and usage examples. |
| get-docsA | Retrieve the full documentation content for a specific route. After finding relevant documentation with search-docs, use this tool to get the complete markdown content including code examples, detailed explanations, and API references. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: get-docs retrieves full documentation content, help explains the server's purpose, search-docs searches documentation by keyword, and version returns the server version. An agent can easily tell these tools apart as they target different functionalities.
The naming is mixed with some consistency issues: get-docs and search-docs follow a verb_noun pattern with hyphens, but help and version are single words without a clear pattern. This mixed convention reduces predictability, though the names remain readable.
With 4 tools, the count is reasonable for a documentation-focused server, covering core operations like searching, retrieving, and getting help. It is slightly under-scoped as it lacks tools for interacting with PDFDancer's actual functionality (e.g., processing PDFs), but the tools provided are well-justified for their stated purpose.
The tool surface is severely incomplete for a server named 'pdfdancer-mcp', which implies PDF manipulation capabilities. It only provides documentation access and meta-tools (help, version), with no tools for creating, editing, or processing PDFs. This creates significant gaps that will cause agent failures when trying to perform PDF-related tasks.