Generating Video, PDFs, and Images with the Claude MCP Server

MCP lets Claude call tools exposed by an external server; it does not make every media-generation service a built-in Claude feature. One documented example is RenderForm’s MCP server: it connects a supported MCP client to RenderForm’s API for template-based image and PDF rendering, webpage screenshots, and webpage-to-PDF conversion. RenderForm’s product page also describes video rendering, but its detailed MCP tool list does not name a video-render tool. Check the tools exposed by your installed version before relying on video generation.

This guide sets up the documented RenderForm server, explains the template-driven workflow, shows how to verify video support, and covers security, troubleshooting, performance, and costs. If your goal is specifically to capture a webpage as an image or PDF, ScreenshotNeo is another option; its one-call API is shown below.

1. What “Claude MCP server” means

There is no single universal “Claude MCP Server.” Claude is the assistant and client; an MCP server exposes tools that the client can call to reach an external system. The Model Context Protocol documentation describes MCP as an open standard for connecting AI applications to external systems. In this example, RenderForm’s server exposes parts of the RenderForm rendering service to compatible clients.

That boundary matters: the service supplies the rendering capability, and its API and templates determine what can be produced. For the documented image and PDF workflow, you select or create a template, provide its dynamic data, and ask Claude to render it. This is useful for repeatable, branded outputs such as reports, cards, and other graphics. It should not be described as arbitrary, unconstrained file design by Claude.

2. Before you connect

• A supported MCP client, such as Claude Desktop, with MCP server configuration available.
• A RenderForm account and API key. Create or retrieve the key in the account’s API Keys area.
• A RenderForm template for the output you want, or permission to create one.
• Node.js and npm available to the client environment, because the documented configuration launches the server with npx.

Use a dedicated API key where possible. The key is placed in your local MCP client configuration and sent to RenderForm’s API by the server. Treat that configuration as a secret: do not paste the key into a public repository, issue, prompt, or shared screenshot.

3. Configure the RenderForm MCP server

1. Open your RenderForm account and copy an API key from the API Keys area.
2. Open the MCP server configuration for your client. The vendor’s documented launch pattern uses stdio and runs renderform-mcp through npx.
3. Insert the configuration below, replacing RENDERFORM_API_KEY with your key. Keep the key private.
4. Save the configuration and restart or reload the client if it does not detect changes automatically.
5. Inspect the client’s available tools. Confirm that the RenderForm tools appear before asking Claude to use them.

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

The exact configuration file location and restart behavior depend on the MCP client. Use that client’s current MCP setup instructions for where this JSON belongs. The command above is the documented vendor pattern; it is not a universal configuration filename.

4. Render an image or PDF from Claude

1. Choose a template in RenderForm, or create one with placeholders for the values that should vary.
2. Note the template name or identifier and the data fields it expects.
3. Ask Claude to render that template and provide values for the placeholders.
4. Review the returned result or file URL. Check that the values, layout, and output format are correct before using the file downstream.

A practical request should name the template and give the values explicitly. For example:

Use the RenderForm tools to render the template named “release-card” as a PNG.
Set the headline to “Version 2.4 released” and the subtitle to “Read the migration notes”.
Return the resulting file URL.

For a PDF, state the intended template and the data clearly. RenderForm’s PDF API workflow is to design a template, send data, then receive a PDF or image. The MCP tools documented by RenderForm include rendering an image or PDF from a template; available formats named in its template rendering documentation include PDF, PNG, and JPG. Ask for the desired output format instead of assuming the server will infer it.

Use the RenderForm tools to render the template named “monthly-report” as a PDF.
Set the report_title to “September summary” and period to “September 2026”.
Return the resulting file URL.

These prompts illustrate how to supply intent and data; the template’s actual fields and the connected tool’s accepted parameters control whether a request succeeds. If Claude asks for missing information, check the template fields and provide the missing values rather than inventing new field names.

5. Can Claude generate video through this server?

RenderForm’s MCP product page describes rendering videos from templates. However, the detailed MCP documentation enumerates image and PDF rendering tools and does not name a video-render tool. Those sources make different levels of promise. Video support therefore depends on the installed server version and the tools your client actually exposes.

Before building a workflow around video:

1. Open the MCP client’s tool list for the connected RenderForm server.
2. Look for an explicitly named video-rendering tool and inspect its input schema.
3. If it is absent, update or install the server version documented by the provider, reconnect, and inspect again.
4. Only then ask Claude to render a video from a template, following the tool’s required fields and output rules.

Do not treat a generic image or PDF rendering tool as evidence of video capability. If the installed tool list still has no video tool, use a documented video workflow from the service directly or choose another supported integration.

6. Other tools and permissions

RenderForm’s detailed MCP documentation lists tools for rendering an image or PDF from a template, taking a webpage screenshot, converting a webpage to PDF, listing and inspecting render results, deleting a render result, listing and inspecting templates, deleting a template, checking organization usage, and listing fonts. The product page’s video description is broader than that detailed tool list, so verify rather than assume which capabilities are available in your installation.

Some listed operations delete resources. Connecting the server makes those tools available to the client, so review the exposed tool list and your team’s key permissions before using it with sensitive work. Avoid asking an assistant to delete a template or render unless that is the intended action; inspect the target first.

7. Webpage screenshots and PDFs

A template render and a webpage capture are different workflows. Use the template workflow for consistent graphics or documents populated by data. Use the webpage screenshot or webpage-to-PDF tools when the source is an existing URL and the goal is to capture its rendered page. The vendor’s tool list includes both webpage screenshot and webpage-to-PDF capabilities, but output behavior depends on the specific tool schema and page.

For page capture, give Claude the exact URL and explain whether you need an image or PDF. For pages requiring authentication, dynamic content, or a particular viewport, inspect the exposed parameters instead of assuming the tool can access private content or wait for a particular state. Never provide account credentials in an ordinary prompt unless your approved workflow specifically supports them and protects them.

8. Or skip the browser setup

If you only need a website screenshot or PDF, ScreenshotNeo provides a direct API and an MCP server for AI agents. Its API accepts one GET request for a URL and returns an image or PDF. See the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

ScreenshotNeo accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. Its MCP server includes take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.

Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.

9. Cost, performance, and reliability

RenderForm’s current MCP product page lists 1 credit per image or PDF render, 10 credits per second of video, and a free allowance of 50 credits. Rates and allowances can change, so check your account’s current usage and plan details before estimating a production workload. Video’s per-second rate means duration should be part of any cost estimate if your connected version supports video rendering.

For repeatable work, reuse a template and change only its data. That makes the output easier to review and avoids asking the model to reconstruct layout instructions on every request. For bulk or automated workflows, check the service API’s current limits and the MCP tool schema; the available dossier does not establish throughput, latency, or uptime figures, so no benchmark or service guarantee should be inferred here.

Validate representative outputs, especially when they include long text, missing fields, or values near layout limits. A successful tool call means the service returned a result, not that every field rendered as intended. Keep the file URL and render result identifier available for review, and use the documented inspection tools where appropriate.

10. Troubleshooting

Symptom	Likely cause	What to do
RenderForm tools do not appear	Invalid client configuration, server failed to launch, or client has not reloaded.	Check the JSON structure, confirm Node.js/npm are available to the client process, verify the command and key argument, then restart or reload the client and inspect its MCP connection status.
Authentication or API request fails	Missing, mistyped, expired, or unauthorized API key.	Copy a valid key from the account API Keys area, update local configuration, and reconnect. Do not include the real key in a support prompt or public log.
Template cannot be found	The prompt names the wrong template, or the connected account cannot access it.	Use the template listing/inspection tools to confirm the exact available template and fields, then retry with that name or identifier.
Output has missing or unexpected content	Data fields do not match the template placeholders, or the requested format was unclear.	Inspect the template, provide all required field values, specify PDF, PNG, or JPG where applicable, and review a new result.
Video request is unavailable	The connected server version may not expose a video tool.	Inspect the actual tool list and schema. Do not assume video is supported from the product-page description alone.
Webpage capture is blank or incomplete	The page may be inaccessible to the capture service or its content may not have loaded as expected.	Confirm the URL is publicly reachable, inspect the tool’s supported wait or capture parameters, and retry. Do not assume authenticated pages can be captured.
A resource was deleted unexpectedly	A destructive delete tool was invoked on the wrong render or template.	Inspect targets before deletion and limit who can use the connected client and key. Check the service for recovery options; none are established here.

11. FAQ

Does MCP make media generation a native Claude feature?

No. Claude calls tools exposed by an MCP server, and the connected external service performs the rendering.

Can Claude create a PDF from a webpage?

RenderForm’s documented tool list includes webpage-to-PDF conversion. That is separate from rendering a PDF from a data-filled template.

Do I need a template?

For RenderForm’s documented image and PDF template workflow, yes: select or create a template and provide its data. Webpage capture is a separate tool path.

Will every MCP client expose the same tools?

Not necessarily. Check the connected client’s tool list and each tool’s schema for the server version you installed.

Sources

• Model Context Protocol documentation — protocol overview.
• RenderForm MCP documentation — setup pattern and enumerated tools.
• RenderForm MCP product page — product claims, credit figures, and video description.
• RenderForm API documentation — template-driven rendering workflow.