Skip to main content
Glama

@rendoc/mcp-server

npm version License: MIT CI

The rendoc MCP server lets AI assistants like Claude Desktop, Cursor, and any other MCP-compatible client generate professional PDF documents on demand. Connect your AI to rendoc and it can create invoices, contracts, reports, certificates, and any other PDF — from reusable templates or inline HTML/Handlebars markup — all from a natural language prompt.

Turn "Generate an invoice for Acme Corp, 40 hours of consulting at €85/h" into a delivered PDF in seconds.

Use Cases

Use Case

Example Prompt

Invoices

"Generate an invoice for client X with these line items..."

Contracts

"Draft a freelance contract for TechStart SL, €18,000 fee, 50% upfront..."

Certificates

"Issue a course completion certificate for María González..."

Reports

"Create a March 2026 sales report with these KPIs..."

Bulk generation

"Generate certificates for all 50 attendees in this CSV"

Custom documents

Anything you can describe in HTML + data

See detailed walkthroughs in examples/.

Related MCP server: PDF Export for AI Agents

Features

  • 7 tools for document generation, template management, and usage tracking

  • Template-based or inline — save reusable templates or pass markup on the fly

  • Handlebars syntax — use {{variables}}, {{#each}}, {{#if}} in your markup

  • Multiple paper sizes — A4, Letter, Legal, A3, A5, portrait or landscape

  • Schema validation — templates can declare a JSON Schema so the AI can't pass invalid data

  • Zero config — just set RENDOC_API_KEY and go

  • Lightweight — ~35 KB unpacked, pure TypeScript, only 2 runtime dependencies

  • Verified on Glama — security, quality, and license checks passed

Quick Setup for Claude Desktop

Add this to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "rendoc": {
      "command": "npx",
      "args": ["-y", "@rendoc/mcp-server"],
      "env": {
        "RENDOC_API_KEY": "your-api-key"
      }
    }
  }
}

Restart Claude Desktop. The rendoc tools will appear in the MCP tools menu.

Quick Setup for Claude Code

Add this to your project or global settings (.claude/settings.json):

{
  "mcpServers": {
    "rendoc": {
      "command": "npx",
      "args": ["-y", "@rendoc/mcp-server"],
      "env": {
        "RENDOC_API_KEY": "your-api-key"
      }
    }
  }
}

Quick Setup for Cursor

Add to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):

{
  "mcpServers": {
    "rendoc": {
      "command": "npx",
      "args": ["-y", "@rendoc/mcp-server"],
      "env": {
        "RENDOC_API_KEY": "your-api-key"
      }
    }
  }
}

Available Tools

Tool

Description

Key Parameters

generate_document

Generate a PDF from a template or inline markup

template_id or markup, data, paper_size?, orientation?, filename?

list_templates

List available document templates

category?

preview_template

Inspect a template's markup, styles, and schema

template_id

create_template

Create a new reusable template

name, slug, markup, schema, category?, styles?, sample_data?, paper_size?, orientation?, is_public?

delete_template

Delete a template by ID

template_id

get_document

Get details of a generated document

document_id

get_usage

View monthly API usage statistics

(none)

Each tool returns structured JSON with download URLs, document IDs, and metadata the assistant can act on.

Get an API Key

  1. Sign up at rendoc.dev

  2. Go to the API Keys dashboard

  3. Create a new key and copy it into your MCP client config

Environment Variables

Variable

Required

Default

Description

RENDOC_API_KEY

Yes

—

Your rendoc API key for authentication

RENDOC_API_URL

No

https://rendoc.dev

Base URL for the rendoc API (useful for self-hosted instances)

Examples

Detailed walkthroughs with real prompts and tool calls:

How It Works

┌──────────────┐   MCP/stdio    ┌────────────────────┐   HTTPS   ┌─────────────┐
│ Claude Code  │ ─────────────▶ │ @rendoc/mcp-server │ ────────▶ │ rendoc API  │
│ / Desktop    │                │   (this package)    │           │  (PDF gen)  │
└──────────────┘ ◀───────────── └────────────────────┘ ◀──────── └─────────────┘
        ▲         tool results                        download URL
        │
        └── User prompt: "Generate an invoice for..."

The MCP server translates natural language tool calls from your AI assistant into authenticated REST requests to the rendoc API, and returns structured responses with PDF download URLs.

Contributing

Contributions are welcome. See CONTRIBUTING.md for development setup and PR guidelines.

For security issues, please see SECURITY.md and email info@rendoc.dev — do not open a public issue.

License

MIT — see LICENSE.

Available Tools

7 tools
create_templateA

Create a new reusable document template. Templates use HTML/Handlebars markup with a JSON schema defining the expected data fields. Once created, use the returned template ID with generate_document to produce PDFs.

Inputs: name (required), slug (required), markup (required), schema (required), +7 more.

delete_templateA

Delete a template by its ID. This action is irreversible. Only templates you own can be deleted.

Inputs: template_id (required).

generate_documentA

Generate a PDF document from a template and data. Returns a download URL for the generated PDF. Provide either template_id (to use a saved template) or markup (inline HTML/Handlebars template). The data object is injected into the template to produce the final document. Supports custom paper sizes, orientation, and filenames.

Inputs: data (required), template_id, markup, paper_size, +2 more.

get_documentA

Get details about a previously generated document by its ID. Returns the document status, download URL, file size, page count, and creation date.

Inputs: document_id (required).

get_usageA

Get current API usage statistics for this billing month. Returns your plan name, document count vs limit, page count, and remaining quota.

Inputs: no named parameters.

list_templatesA

List available document templates. Optionally filter by category. Returns template names, slugs, categories, descriptions, paper sizes, and IDs. Use the returned ID with generate_document or preview_template.

Inputs: category.

preview_templateA

Get the full markup, styles, and data schema of a template. Use this to inspect a template before generating a document. The schema shows which data fields the template expects. Sample data (if available) shows example values for each field.

Inputs: template_id (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: create_template, delete_template, list_templates, and preview_template handle template management; generate_document and get_document handle document generation and retrieval; get_usage provides API usage stats. The descriptions reinforce these boundaries, making tool selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_template, generate_document, get_usage). The verbs are clear and appropriate for their actions, and there are no deviations or mixed conventions throughout the set.

    Tool Count5/5

    With 7 tools, the server is well-scoped for document generation and template management. Each tool earns its place by covering essential operations like CRUD for templates, document generation, retrieval, and usage monitoring, without being too sparse or bloated.

    Completeness5/5

    The tool set provides complete coverage for the document generation domain: full CRUD for templates (create, delete, list, preview), document generation and retrieval, and usage monitoring. There are no obvious gaps, and the tools support core workflows from template creation to PDF output without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers