OJo — HTML to image

What oJo — HTML to image does

oJo — HTML to image lets an MCP-compatible agent turn HTML or Handlebars content into browser previews, PNG images, and PDFs. The server communicates with an MCP client over local stdio. When an API key is available, it also connects to the oJo API at https://api.ojo.so/v1 for hosted output and template operations.

The service supports two rendering paths. Agents can provide plain HTML with inline CSS, or select an existing reusable template and supply replacement values. Template tools expose the account's available templates, return a template's decoded HTML and default variables, and create new templates from HTML or Handlebars.

How it works

The recommended workflow starts with create_preview_link. It produces an https://ojo.so/preview#draft=… URL containing a compressed draft in the URL hash. The draft is rendered in the browser by the same engine used for the final PNG, and the content is not sent to a server or stored by the preview flow. This makes the link suitable for sharing a draft with a reviewer before committing a render.

After reviewing the preview, an agent can call an image or PDF generation tool. Image rendering returns a public PNG URL. PDF rendering returns a public PDF URL and page count, supports up to 20 pages, and uses A4 unless the HTML includes a CSS @page rule that changes the page size. Requests longer than 20 pages are refused without consuming a credit.

Both image-generation tools support inspect: true, which adds a 512-pixel-wide thumbnail to confirm that rendering succeeded. The thumbnail is intended for basic validation rather than detailed layout or typography review. PDF previews show screen rendering and do not demonstrate final page breaks.

Setup and configuration

Install and launch the package through npx:

{
  "mcpServers": {
    "ojo": {
      "command": "npx",
      "args": ["-y", "@ojodotso/mcp-server"]
    }
  }
}

No account or key is needed for preview-only mode. Set OJO_API_KEY to enable hosted PNG and PDF URLs plus reusable template operations. OJO_API_BASE_URL can replace the default API endpoint, while OJO_WEB_BASE_URL changes the web application used for preview links; the latter is useful when developing against a local web app.

Tools and capabilities

• create_preview_link creates a free, full-resolution preview for HTML or Handlebars drafts.
• generate_image_from_html renders inline-styled HTML as a PNG.
• generate_image_from_template renders a stored template with optional per-render overrides.
• generate_pdf_from_html creates a PDF from HTML and reports its page count.
• generate_pdf_from_template renders a stored template as a PDF.
• list_templates, get_template, and create_template support template management.

Only the preview tool is registered without an API key. The remaining tools require authenticated access to the oJo API, and image or PDF generation uses one credit per render.

Limitations and notes

oJo — HTML to image accepts plain HTML with inline CSS for direct rendering. Template rendering depends on templates already available to the account or created through the template tools. Preview links are not a substitute for checking PDF pagination, and the optional inspection thumbnail is too small for precise visual review. The server uses stdio locally; its remote boundary is HTTP to the configured oJo API and preview web application.