MCP and HTTP API

Publish pages programmatically: add rendrd as an MCP server so an AI assistant can publish for you, or POST HTML to the HTTP API from any language.

Get an API key

Create one under Settings in your rendrd account. Send it as Authorization: Bearer YOUR_API_KEY. Treat it like a password.

MCP server

MCP URL	https://rendrd.io/mcp/sse
Auth	Authorization: Bearer YOUR_API_KEY
Tools	rendrd_publish, rendrd_list

Claude (web and mobile)

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Paste the MCP URL and your API key, then Add.
4. In any chat, open the + menu and turn rendrd on.

ChatGPT (web)

1. Settings → Connectors → Advanced settings, turn on Developer mode.
2. Settings → Connectors → Create.
3. Name it rendrd, paste the MCP URL, add your API key, then Create.

Claude Code

claude mcp add --transport sse rendrd \
  https://rendrd.io/mcp/sse \
  --header "Authorization: Bearer YOUR_API_KEY"

Gemini CLI

The Gemini web app does not support custom MCP servers yet. Use the CLI: add rendrd to ~/.gemini/settings.json under mcpServers, then restart.

{
  "mcpServers": {
    "rendrd": {
      "url": "https://rendrd.io/mcp/sse",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

HTTP API

No MCP needed. POST the HTML directly.

curl -X POST https://rendrd.io/api/publish \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"html":"<!doctype html>…","title":"Q4 Report"}'

# → { "url": "https://view.rendrd.io/q4-report", … }

POST /api/publish

Field	Type	Notes
html	string	Required. The self-contained HTML document.
title	string	Optional. Used for the link name and previews.
slug	string	Optional. Custom link name (paid plans).
password	string	Optional. Visitors must enter it to view.

The HTML is sanitised on publish against the accepted-frameworks policy. The same rules apply whether you publish from the website, the MCP server or the API.