renderform-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENDERFORM_API_KEY | Yes | Your RenderForm API key. Can also be passed via --api-key argument. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_imageA | This tool renders an image, PDF or video from a RenderForm template.
|
| create_screenshotB | This tool captures a screenshot of a web page using RenderForm.
|
| create_pdfA | This tool converts a web page into a PDF using RenderForm.
|
| get_render_resultsA | This tool lists past render results (images, PDFs, screenshots) in your RenderForm account.
|
| get_render_resultA | This tool retrieves details of a single render result by its identifier (requestId).
|
| delete_render_resultA | This tool permanently deletes a render result (and its file) from your RenderForm account.
|
| get_templatesA | This tool lists templates available in your RenderForm account.
|
| get_templateA | This tool retrieves the full details of a single template, including its editable 'properties' (component IDs, property names and default values), fonts and tags.
|
| delete_templateA | This tool permanently deletes a template from your RenderForm account.
|
| get_usageA | This tool returns the organization's usage summary: render credits (used/total/renewal), file storage uploads (used/total bytes) and plan/billing status.
|
| get_fontsA | This tool lists fonts available in your RenderForm account, including Google fonts and any custom uploaded fonts.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.