Skip to main content
Glama
renderform-mcp

renderform-mcp

Official
by RenderForm

MCP Server for RenderForm

RenderForm is an API for automatically generating images, PDFs, screenshots and videos from templates.

This is a Model Context Protocol (MCP) server that provides tools for interacting with the RenderForm API.

Features (Tools)

  • Render an image/PDF from a template

  • Create a screenshot of a web page

  • Convert a web page to PDF

  • List render results

  • Get render result details

  • Delete a render result

  • List templates

  • Get template details

  • Delete a template

  • Get organization usage (credits, uploads, plan)

  • List available fonts

Feel free to add more tools by making a pull request or creating a feature request.

Related MCP server: doc-ops-mcp

Installation

To use the MCP server, you'll need an API key. You can create and manage API keys in RenderForm > Settings > API Keys.

To run the server in a client like Claude Desktop, Cursor or Windsurf, add the following to your MCP config:

{
  "servers": {
    "renderform": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "renderform-mcp", "--api-key=RENDERFORM_API_KEY"]
    }
  }
}

Replace RENDERFORM_API_KEY with your API key.

For detailed setup guides, see:

Development

  1. Install dependencies:

    npm install
  2. Build the server:

    npm run build
  3. Update client to use the local build:

    {
      "servers": {
        "renderform": {
          "command": "node",
          "args": ["path/to/renderform-mcp/build/index.js"],
          "env": {
            "RENDERFORM_API_KEY": "your_api_key"
          }
        }
      }
    }

Debugging

To debug the MCP server, you can use the MCP Inspector tool:

  1. Run the server with the inspector:

    npm run inspector
  2. Open the provided URL in your browser to view and debug the MCP requests and responses.

  3. Include the --api-key argument.

Learn more

Available Tools

11 tools
create_pdfA

This tool converts a web page into a PDF using RenderForm.

  • Provide 'url' (required).

  • Optionally provide 'format' (A5, A4, A3, LETTER or LEGAL - defaults to A4), 'waitTime' (ms, 0-5000) before capturing, and 'expires' (seconds, 1-604800) to auto-delete the generated PDF.

Inputs: url (required), format, expires, waitTime.

create_screenshotB

This tool captures a screenshot of a web page using RenderForm.

  • Provide 'url' (required), 'width' and 'height' (required, 32-5000px).

  • Optionally provide 'waitTime' (ms, 0-5000) to wait before capturing, useful for pages with animations or async content.

Inputs: url (required), width (required), height (required), waitTime.

delete_render_resultA
Destructive

This tool permanently deletes a render result (and its file) from your RenderForm account.

  • Provide 'identifier' (required), the requestId of the result to delete.

  • This action is destructive and cannot be undone.

Inputs: identifier (required).

delete_templateA
Destructive

This tool permanently deletes a template from your RenderForm account.

  • Provide 'templateId' (required).

  • This action is destructive and cannot be undone.

Inputs: templateId (required).

get_fontsA
Read-onlyIdempotent

This tool lists fonts available in your RenderForm account, including Google fonts and any custom uploaded fonts.

  • No parameters required.

  • Use this to find a valid font family name to use in a template.

Inputs: no named parameters.

get_render_resultA
Read-onlyIdempotent

This tool retrieves details of a single render result by its identifier (requestId).

  • Provide 'identifier' (required), returned as 'requestId' from the render/screenshot/pdf tools.

  • Returns status, dimensions, href, template info and timestamps.

Inputs: identifier (required).

get_render_resultsA
Read-onlyIdempotent

This tool lists past render results (images, PDFs, screenshots) in your RenderForm account.

  • Optionally filter by 'template' or 'batch' identifier.

  • Supports pagination with 'page' (default 0) and 'size' (default 20, max 50).

Inputs: page, size, batch, template.

get_templateA
Read-onlyIdempotent

This tool retrieves the full details of a single template, including its editable 'properties' (component IDs, property names and default values), fonts and tags.

  • Provide 'templateId' (required).

  • Use the returned 'properties' to build the 'data' object for the 'render_image' tool.

Inputs: templateId (required).

get_templatesA
Read-onlyIdempotent

This tool lists templates available in your RenderForm account.

  • Optionally filter by 'name', 'tags' or 'sourceTemplateId'.

  • Supports pagination with 'page' (default 0) and 'size' (default 20, max 50).

  • Use this to find a template identifier before rendering or fetching template details.

Inputs: name, page, size, tags, +1 more.

get_usageA
Read-onlyIdempotent

This tool returns the organization's usage summary: render credits (used/total/renewal), file storage uploads (used/total bytes) and plan/billing status.

  • No parameters required.

  • Use this to check remaining credits before running large render batches.

Inputs: no named parameters.

render_imageA

This tool renders an image, PDF or video from a RenderForm template.

  • Provide 'template' (required): the template ID, e.g. template_1234.

  • Provide 'data' to merge dynamic content into the template. Keys follow the 'componentId.property' convention (e.g. { "my-text.text": "Hello World!", "my-image.src": "https://example.com/image.jpg" }).

  • Component IDs and editable properties can be discovered with the 'get_template' tool (see the 'properties' field of the template).

  • Optionally provide 'fileName', 'webhookUrl' (called when the render finishes), 'version' (cache key - reusing it returns a cached result instead of re-rendering), 'metadata' (passed through to the webhook), 'batchName' (to group renders together) and 'waitTime' (delay before rendering, max 5000ms).

  • Use 'output: json' (default) to get back a JSON object with the href of the rendered file. Avoid 'output: image' here since it returns raw binary bytes.

Inputs: template (required), data, output, version, +5 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: PDF from URL, screenshot from URL, render from template, CRUD for templates and render results, listing fonts and usage. No overlapping functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with lowercase snake_case (e.g., create_pdf, get_templates, render_image). No deviations or mixed styles.

    Tool Count5/5

    11 tools cover the essential operations for a render service: creating, listing, deleting renders and templates, plus utility tools for fonts and usage. Neither too few nor too many.

    Completeness4/5

    Core workflows are covered: browse templates, render, check results, delete, check usage. Missing create/update template and font upload, but these may be out of scope. Minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers