renderform-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@renderform-mcp render an image from template 'social post' with text 'Hello World'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Install dependencies:
npm installBuild the server:
npm run buildUpdate 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:
Run the server with the inspector:
npm run inspectorOpen the provided URL in your browser to view and debug the MCP requests and responses.
Include the
--api-keyargument.
Learn more
Available Tools
11 toolscreate_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_resultADestructive
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_templateADestructive
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_fontsARead-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_resultARead-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_resultsARead-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_templateARead-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_templatesARead-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_usageARead-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
Scored across 11 tools
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.
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.
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.
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
Related MCP Connectors
AutoRender's MCP server for media assets, transformations, delivery, and workflow automation.
MCP server for Api2Pdf — generate PDFs & images from HTML, URLs or office files; merge, barcodes.
Screenshots, PDFs, image editing, QR codes, email validation and more through one hosted MCP server.
A remote MCP server to convert HTML documents (URL or raw source) to PDF or screenshots
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server for image processing and cloud uploads that automates resizing, converting, optimizing, and uploading images to services like AWS S3, Cloudflare R2, and Google Cloud Storage.14 npm18MIT
- AlicenseBqualityDmaintenanceA universal MCP server for document processing, conversion, and automation. Handle PDF, DOCX, HTML, Markdown, and more through a unified API and toolset.1318 npm140MIT
- AlicenseAqualityBmaintenanceMCP server for the OpenGraph.io API -- extract OG metadata, capture screenshots, scrape pages, query sites with AI, and generate branded images with iterative refinement.11182 npm2ISC

vidhook-mcpofficial
AlicenseAqualityCmaintenanceAn MCP server enabling agents to generate videos via the vidhook render API, with tools to validate movie definitions, start renders, and check status.310 npmMIT