MCP server for Rendex: render HTML, Markdown, or URLs to images or PDF, apply Mustache data templating, and extract clean reader-mode content, all
Connect Rendex MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Rendex: render HTML, Markdown, or URLs to images or PDF, apply Mustache data templating, and extract clean reader-mode content, all from AI agents. The rendex mcp mcp server is what makes that connection.
MCP server for Rendex — render raw HTML, Markdown, or any URL to an image or PDF via AI agents using the Model Context Protocol.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
rendex_screenshot — Render any webpage, raw HTML, or Markdown to an image or PDFrendex_extract — Extract clean reader-mode content from any webpage as Markdown, JSON, or HTML. Runs the same Chromium render pass as a screenshot, so it capturesrendex_render_link — Render a URL, raw HTML, or Markdown and get back a signed, hosted, edge-cached image URL instead of the bytes — ideal for dynamic OG images. Droprender_artifact — Turn Markdown or HTML into a branded, downloadable artifact — a PDF, a PNG, and a hosted share page — in one call. Ideal for agent outputsrendex_account — Check the account from inside the agent: which plan it's on, how many render credits have been used this month vs. the limit (and when it resets)Configuration is passed through the environment: RENDEX_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Rendex MCP's toolset — rendex_screenshot, rendex_extract, rendex_render_link and 2 more — is a fair guide to whether it matches your workflow. It is maintained by copperline-labs; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| rendex_screenshot | Render any webpage, raw HTML, or Markdown to an image or PDF. |
| rendex_extract | Extract clean reader-mode content from any webpage as Markdown, JSON, or HTML. Runs the same Chromium render pass as a screenshot, so it captures content **after JavaScript runs** — handling SPAs that fetch-only readers |
| rendex_render_link | Render a URL, raw HTML, or Markdown and get back a **signed, hosted, edge-cached image URL** instead of the bytes — ideal for dynamic OG images. Drop the URL into <meta property="og:image"> or an tag and Rendex serves a |
| render_artifact | Turn Markdown or HTML into a **branded, downloadable artifact — a PDF, a PNG, and a hosted share page — in one call**. Ideal for agent outputs: reports, invoices, summaries, release notes, dashboards. Apply a logo, accen |
| rendex_account | Check the account from inside the agent: which plan it's on, how many render credits have been used this month vs. the limit (and when it resets), the per-minute rate limit, and a one-tap upgrade link. Lets an agent answ |
{
"mcpServers": {
"rendex": {
"command": "npx",
"args": ["-y", "@copperline/rendex-mcp"],
"env": {
"RENDEX_API_KEY": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| RENDEX_API_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.