docjet-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCJET_API_KEY | Yes | Your DocJet API key (binfra_ prefix). Sent as a Bearer token; never logged. | |
| DOCJET_BASE_URL | No | Override the API base URL (default https://api.docjet.dev). | https://api.docjet.dev |
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 |
|---|---|
| render_pdfA | Render a branded PDF document with the DocJet API. Provide a template_id (discover them with list_templates) or raw html, plus a data object for template variables. Returns a signed download URL for the PDF. |
| render_imageA | Render a PNG image (e.g. an OG/social card) with the DocJet API. Provide a template_id (discover them with list_templates) or raw html, plus a data object for template variables. Returns a signed download URL for the PNG. |
| list_templatesA | List the available DocJet templates: id, name, description and outputType (pdf or png). Use a returned id as template_id in render_pdf / render_image. |
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 3 tools
Each tool has a clearly distinct purpose: listing templates, rendering to PNG, and rendering to PDF. No functional overlap.
All tool names follow a consistent verb_noun pattern: list_templates, render_image, render_pdf.
With only 3 tools, the set is tightly scoped to the core functionality of template discovery and rendering, which is appropriate for this service.
The tools cover the primary use case of listing and rendering templates. The ability to provide raw HTML compensates for missing template management, though a tool to create/update templates would be a minor gap.