mcp-pandoc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | Your token used for publishing to PyPI | |
| UV_PUBLISH_PASSWORD | No | Your password for publishing to PyPI | |
| UV_PUBLISH_USERNAME | No | Your username for publishing to PyPI |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert-contentsA | Converts content between different formats. Transforms input content from any supported format into the specified output format. šØ CRITICAL REQUIREMENTS - PLEASE READ:
Supported formats:
ā INCORRECT Usage Examples:
When requesting conversion, ALWAYS specify:
šØ DOCX, ODT & PPTX STYLING: 4. Custom Styling with Reference Documents:
šÆ PANDOC FILTERS (NEW FEATURE): 5. Pandoc Filter Support:
š Creating Reference Documents:
š Filter Requirements:
š Defaults File Support (NEW FEATURE): 7. Pandoc Defaults File Support:
Note: After conversion, always check the success message for the exact file location. |
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
There is only one tool, so there is no possibility of an agent mistaking it for another. Its purpose is clearly defined as content conversion, with no overlapping tools.
Although there is only one tool, the name 'convert-contents' follows a clear verb_noun convention and is semantically appropriate. With no other tools, there are no naming conflicts or mixed conventions.
A single tool for Pandoc conversion feels minimal, though it can cover many conversions through its parameters. It is on the thin side of the acceptable range for a focused converter server.
The tool supports conversion across a wide range of formats, including inline returns and file outputs, plus advanced options like reference documents, filters, and defaults files. For a conversion-only server, this covers the domain thoroughly with no obvious operational gaps.