Sheetrender MCP Server

@sheetrender/mcp

MCP server for SheetRender. It lets your AI assistant render PDFs from HTML templates and spreadsheet data.

Setup

Get an API key from sheetrender.com under Settings → API keys, then add this to your MCP client config:

{
  "mcpServers": {
    "sheetrender": {
      "command": "npx",
      "args": ["-y", "@sheetrender/mcp"],
      "env": { "SHEETRENDER_API_KEY": "sr_live_..." }
    }
  }
}

SHEETRENDER_API_URL is also read, and defaults to https://sheetrender.com. Set it only if you're pointing at a self-hosted or staging instance.

Tools

render_pdf

Renders one PDF from HTML you supply.

Returns the path of the saved PDF and its size. Under 512 KB it's also attached inline as a base64 resource, so clients that display attachments show the document itself.

Two server limits apply. HTML over 2 MB is rejected, and that's measured both on what you send and on the document after data is substituted in, so a template that expands a long dataset can cross the line even when the markup you wrote doesn't. The other is the free plan, where every rendered PDF carries a "Made with SheetRender" footer. That applies to render_pdf and render_template alike. Paid plans don't get it.

list_templates

No arguments. Returns each saved template's name, id and last-updated date. Call it to turn a template name the user mentioned into the id the other tools want.

render_template

Renders one PDF from a template already saved in the account.

Same return as render_pdf.

create_batch_job

Queues a background job that renders one PDF per row of a dataset already uploaded to the project. This server can't upload spreadsheets.

Returns the job id to poll with get_job. Worth knowing: filename_template and group_by are persisted to the template and the project respectively, so they change the defaults for later runs too.

If the server predates the public batch endpoint, the tool reports that batch jobs are unavailable rather than failing obscurely.

get_job

Takes job_id. Returns the status, rows done and failed, and the id and filename of every rendered document. That document list stays empty while the job is queued, retry_queued or running, and fills in once the job reaches succeeded, partial, failed or cancelled. Those document ids are what get_document takes.

get_document

Takes document_id and downloads that single rendered PDF. The ids come from get_job on a finished batch, and there's no other way to get one. Same return as render_pdf: path, size, and an inline blob under 512 KB.

If you want a whole batch, the merged PDF and ZIP in the web app beat fetching each document in turn.

page_settings

Shared by both render tools. Every field is optional:

{
  "page_size": "a4",
  "orientation": "portrait",
  "margins": { "top": 15, "right": 15, "bottom": 15, "left": 15 }
}

page_size is lowercase: a3, a4, a5, letter, legal or tabloid. Margins are plain numbers in millimetres, not CSS lengths.

Rendered PDFs are written to the system temp directory. API errors like a bad key, a missing template or a rate limit come back as tool errors carrying the server's own message.

The public API allows 120 requests per minute per API key. Past that it returns 429, and the tool reports that you're rate limited and should retry shortly. Batch job creation is metered separately and more tightly.

Development

You don't need node or npm on the host: scripts/dev.sh install, then scripts/dev.sh deno task build.

MIT licensed.