HTML to Image API on Smithery

If your team picks its MCP tools through Smithery, HTML to Image is there. The official server is published on the registry as html2img/html2img, maintained by us, and it points back at html2img.com/mcp as its homepage. This page covers the Smithery side: what the listing gives you, how to try the server before configuring anything, and how connecting through Smithery relates to connecting directly.

If you are not using Smithery at all, you want the MCP overview and the installation guide instead; nothing about the server requires Smithery.

What the listing is

Smithery is a registry and platform for MCP servers: a place to search for a capability, read a server’s tool schemas, exercise it in a sandbox and connect it to your client. The html2img/html2img entry is the official listing for the HTML to Image MCP server, published under our own account.

The listing documents the server’s two tools, with their full typed input schemas rendered on the page:

• generate-image-from-html renders HTML and CSS the model writes into a PNG, or into an A4 vector PDF.
• screenshot-url captures a live, public web page by URL, again as a PNG or a PDF.

Each successful image costs one credit, the same credit the REST API uses. The tools reference documents every parameter; the schemas on the Smithery listing are generated from the same definitions, so the two never disagree.

Try it in the playground

The quickest thing the listing offers is Try now: Smithery’s in-browser playground, which talks to the same hosted server your editor would. You can ask for a render, watch the tool call go out and see the image come back without touching a config file.

You will need an API key to render. The server is part of the paid plans, so pick one on the pricing page, create a key on the API keys page (keys look like htim_...), and treat it like a password wherever you paste it. Playground renders are real renders: they spend the same one credit each and the output lands on the same CDN.

Connect a client through Smithery

From the listing, Smithery’s connect flow (Add to toolbox, plus its per-client instructions) walks you through attaching the server to the clients it supports, with your API key supplied as the server’s auth. What Smithery is doing under the hood is pointing your client at the same remote endpoint the installation guide documents, so there is no Smithery-specific behaviour to learn and no extra html2img charge for arriving this way.

Connecting directly instead

Smithery is a convenience, not a dependency. Every MCP client that supports remote HTTP servers can reach the server with three facts:

• URL: https://app.html2img.com/mcp
• Transport: Streamable HTTP
• Auth: the header Authorization: Bearer YOUR_API_KEY

In Claude Code that is one command:

claude mcp add --transport http html2img https://app.html2img.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

The installation guide has the equivalent config for Cursor, VS Code, Windsurf, Antigravity, Gemini CLI, Codex and Claude Desktop, plus the reason ChatGPT cannot connect yet. Signed-in users can copy a pre-filled config from app.html2img.com/mcp-setup.

FAQ

Is the Smithery listing official? Yes. html2img/html2img is published and maintained by us, and its homepage field points back to html2img.com/mcp. Treat any other listing claiming to be this API as unofficial.

Do I need a Smithery account? Not for the server. Browsing the listing is open, while the playground and the toolbox flow follow Smithery’s own account rules. Connecting directly with the config above never involves Smithery at all.

Does connecting through Smithery cost extra? Nothing extra from us: it is the same server, the same key and the same one credit per image whichever way your client reaches it.

Why does the server ask for a paid plan? MCP access is part of the paid plans, from $9 a month. The 50 free signup credits work against the REST API and the free tools, so you can evaluate the renderer itself before subscribing.

Which clients can connect? Claude Code, Cursor, VS Code, Windsurf, Antigravity, Gemini CLI and the Codex CLI natively, and Claude Desktop through a small bridge. The installation guide has the exact config for each.

Where do I learn what the tools can do? The MCP overview shows what assistants build with it, and the tools reference documents both tools parameter by parameter. The schemas on the Smithery listing match the reference.