Skip to main content
Glama
Sign In
docrenders-mcp

docrenders-mcp

by JWhist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

docrenders-mcp

MCP server for DocRenders — generate production-ready PDFs from Claude and any MCP-compatible AI agent.

Tools

Tool

Description

render

Convert Markdown or HTML to a PDF

render_template

Generate a PDF from a built-in template with structured data

list_templates

List all available templates and their fields

get_usage

Check current period render usage

Related MCP server: DocAPI MCP

Setup

1. Get a DocRenders API key

Sign up at docrenders.com and generate an API key from your dashboard.

2. Add to Claude Desktop

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "docrenders": {
      "command": "npx",
      "args": ["-y", "docrenders-mcp"],
      "env": {
        "DOCRENDERS_API_KEY": "dcr_live_YOUR_API_KEY"
      }
    }
  }
}

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

3. Restart Claude Desktop

The DocRenders tools will be available in your next conversation.

Usage examples

Once configured, you can ask Claude things like:

"Generate an invoice PDF for Acme Corp for $2,500 of design work, due June 17."

"Create a PDF resume for Jordan Whistler, senior Go engineer, with experience at Acme and Startup Co."

"Convert this markdown report to a PDF with the ai-summary template."

"How many renders have I used this month?"

Available templates

Template

Required fields

invoice

name, date, total, items

receipt

merchant, date, total, items

resume

name, email

ai-summary

title, date, summary

report

title, author, date, sections

letter

sender_name, recipient_name, date, body, signature_name

proposal

title, client, date, prepared_by, sections

See docrenders.com/docs for full field reference.

Development

git clone https://github.com/JWhist/docrenders-mcp
cd docrenders-mcp
npm install
npm run build
DOCRENDERS_API_KEY=dcr_live_... node dist/index.js

License

MIT

Available Tools

6 tools
get_templateB

Get the full field schema for a specific DocRenders template, including field types, descriptions, and examples.

Inputs: name (required).

get_usageA

Check the current period render usage for the authenticated DocRenders account.

Inputs: no named parameters.

list_templatesA

List all available DocRenders templates with their categories, tags, and field schemas. Supports optional filtering by category or tag.

Inputs: category, tag.

renderA

Convert Markdown or HTML to a PDF. Returns a signed download URL valid for 15 minutes.

Inputs: markdown, html, template, filename, +6 more.

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.

Inputs: template (required), data (required), filename, format, +5 more.

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.

Inputs: template (required), data.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tool names use consistent snake_case with verb_noun pattern (e.g., list_templates, render_template). The pattern is predictable and clear.

    Tool Count5/5

    Six tools cover all necessary operations for a document rendering service: template discovery, rendering, and usage monitoring. Neither too few nor too many.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers