docrenders-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCRENDERS_API_KEY | Yes | Your DocRenders API key |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| renderA | Convert Markdown or HTML to a PDF. Returns a signed download URL valid for 15 minutes. |
| render_templateA | Generate a PDF from a DocRenders template by passing structured data. The template provides the document layout and styling. Use list_templates to see available templates and their required fields, or get_template for a specific template's schema. |
| list_templatesA | List all available DocRenders templates with their categories, tags, and field schemas. Supports optional filtering by category or tag. |
| get_templateB | Get the full field schema for a specific DocRenders template, including field types, descriptions, and examples. |
| render_template_previewA | Generate a preview PDF for a DocRenders template using its built-in preview_fields data. Returns a signed download URL. Previews are cached — repeated calls for the same template return instantly. Does not count against your render quota. |
| get_usageA | Check the current period render usage for the authenticated DocRenders account. |
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 6 tools
Each tool has a distinct purpose: template listing/schema retrieval, generic rendering, template-based rendering with data or preview data, and usage checking. No overlap.
All tool names use consistent snake_case with verb_noun pattern (e.g., list_templates, render_template). The pattern is predictable and clear.
Six tools cover all necessary operations for a document rendering service: template discovery, rendering, and usage monitoring. Neither too few nor too many.
The tool set provides full lifecycle coverage: listing templates, getting their schemas, rendering documents (both generic and template-based), previewing templates without quota cost, and checking usage. No obvious gaps.