- Docs
- Integrations
- MCP server
- Set up HCTI in Windsurf
Set up HCTI in Windsurf
Capture a webpage or turn HTML/CSS into a PNG, WebP, or PDF with HTML/CSS to Image.
You’ll need: an HCTI account with image credits. Sign in through your browser when connecting—no API key to copy.
1. Connect HCTI to Cascade
Section titled “1. Connect HCTI to Cascade”Merge this entry into ~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "hcti": { "serverUrl": "https://mcp.hcti.io" } }}- Save the configuration and refresh the servers in Cascade’s MCP settings.
- Enable HCTI and use its authentication action to authorize your account in the browser.
- Open a Cascade conversation and ask “Use HCTI to check my image usage and account limits”.
You can access the configuration through the client’s MCP settings. The Cascade MCP documentation describes remote HTTP servers and team controls; its documentation now lives under Devin Desktop.
2. Take a screenshot
Section titled “2. Take a screenshot”Send this prompt after connecting:
Use HTML/CSS to Image to screenshot https://example.com as a PNG.Set viewport_width to 1440 and device_scale to 1. Return the image URL.Open the returned image URL to view your screenshot. Replace https://example.com with your own public URL.
3. Render HTML/CSS
Section titled “3. Render HTML/CSS”Try a small card with explicit text, colors, and dimensions:
Use HCTI to render this HTML and CSS as a PNG at device_scale 1.HTML: <div class="card">Hello from HCTI</div>CSS: .card { width: 1200px; height: 630px; display: flex;align-items: center; justify-content: center; background: #172554;color: white; font: 64px sans-serif; }Return the hosted image URL.The result is a dark blue card with centered white text. Edit the text or CSS and render again to refine it.
How to create card variations with Cascade
Section titled “How to create card variations with Cascade”After rendering a card, ask Cascade:
Use HCTI to check my maximum batch size. Render five versions of this HTML/CSS card with different accent colors. Keep the text and layout identical and return a labeled list of image URLs.Checking the account limit first lets Cascade choose a supported batch size. Shared layout options can stay in default_options while individual colors vary.
Available tools
These core tools work across MCP clients. Access depends on the permissions approved for your connection. Ask your assistant to use HCTI by name.
Account usage
| Tool | What it does |
|---|---|
check_usage | Check images used, image allowance, next reset, and overage settings without rendering an image. |
Screenshots and rendering
| Tool | What it does |
|---|---|
create_image | Render HTML/CSS as PNG, JPG, WebP, or PDF. Supports device_scale, viewport_width, viewport_height, and ms_delay. |
create_url_image | Capture a public page or CSS selector, with viewport settings and cookie-banner blocking. |
create_templated_image | Render a saved template with template_id and template_values. |
create_batch_images | Render variations with shared default_options and per-image variations. |
get_max_batch_size | Check the account's batch limit before preparing a batch. |
Template management
| Tool | What it does |
|---|---|
create_template | Save HTML/CSS as a reusable template with variables. |
update_template | Update an existing template by ID. |
list_templates | Find templates in the connected account. |
list_template_versions | Inspect a template's version history. |
See rendering parameters and the Template Editor for image options and reusable designs. The complete tools reference also covers proxies, storage destinations, Open Graph configurations, and required permissions.
Troubleshooting
Section titled “Troubleshooting”For a permission-denied error, reconnect and approve the required access before retrying. Usage checks and maximum batch-size checks require usage:read.
Missing tools or connection errors
Section titled “Missing tools or connection errors”Refresh the MCP servers after editing the configuration, and confirm HCTI tools are enabled in Cascade. If a team allowlist is configured, it must permit the hcti server. Reconnect the account if authorization has expired.
Rendering errors
Section titled “Rendering errors”HCTI fetches webpages from its hosted service. Use a publicly accessible URL; it cannot reach your computer’s localhost. For HTML/CSS rendering, supply the file contents and accessible assets rather than local file paths. Check your HCTI dashboard for available image credits.
See shared MCP troubleshooting for authentication and rendering errors, or choose another client.
Need help?
Talk to a human. Email support@htmlcsstoimage.com and we’ll help you get started.