RenderForm MCP integration for AI agents.
Connect AI agents to RenderForm through 6 structured actions, including get template, render image, and get usage. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the RenderForm integration exposes
The RenderForm Agent App exposes 6 provider-backed actions for design & media and developer tools work. Its current contract lets an authorized agent get one renderform template by identifier and return its normalized template details, render one renderform image or pdf from a template and return the request identifier, file url, and echoed request, and get current renderform credit usage for the api key and return a normalized usage summary. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected RenderForm account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real RenderForm capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_templateREADGet one RenderForm template by identifier and return its normalized template details.
INPUTS: templateId
render_imageREVIEWRender one RenderForm image or PDF from a template and return the request identifier, file URL, and echoed request.
INPUTS: template / data / fileName / webhookUrl / metadata
get_usageREADGet current RenderForm credit usage for the API key and return a normalized usage summary.
list_resultsREADList RenderForm generated results with pagination and optional template or batch filters.
INPUTS: page / size / batch / template
list_templatesREADList RenderForm templates with optional pagination and filters for name, tags, and source template ID.
INPUTS: name / page / size / tags / sourceTemplateId
take_screenshotREVIEWCapture one website screenshot with RenderForm and return the request identifier, file URL, and echoed request.
INPUTS: url / width / height / waitTime
INPUT CONTRACTS
Know what the action needs before it runs.
get_template
templateIdOPTIONAL- Template identifier to retrieve.
render_image
templateREQUIRED- Template identifier to render.
dataOPTIONAL- Template data object forwarded to RenderForm for placeholder replacement.
fileNameOPTIONAL- Optional custom output file name.
webhookUrlOPTIONAL- Optional webhook URL called by RenderForm after rendering completes.
metadataOPTIONAL- Arbitrary metadata object stored together with the generated RenderForm result.
list_results
pageOPTIONAL- Zero-based page number.
sizeOPTIONAL- Number of results to return per page.
batchOPTIONAL- Optional batch identifier filter.
templateOPTIONAL- Optional template identifier filter.
list_templates
nameOPTIONAL- Optional template name filter.
pageOPTIONAL- Zero-based page number.
sizeOPTIONAL- Number of templates to return per page.
tagsOPTIONAL- Template tags used to filter the template list.
sourceTemplateIdOPTIONAL- Optional source template identifier used to filter cloned templates.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Template
Get one RenderForm template by identifier and return its normalized template details. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_templateVerify with Get Usage
Get current RenderForm credit usage for the API key and return a normalized usage summary. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_usageSAFETY BOUNDARY
Operate RenderForm with explicit limits
- Authorize RenderForm with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned RenderForm data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in RenderForm rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the RenderForm task completed successfully.
CONNECTION MODEL
API key
RenderForm API key used with the X-API-KEY header. Create or copy it from the RenderForm API Keys tab: https://renderform.io/console/account/api-keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by RenderForm.