Rendex: Rendering API For Images, PDFs & Content Extraction
Turn HTML, Markdown, or live URLs into shareable PNGs, PDFs, and clean reader extracts from your agent.
Overview
rendex-mcp is an MCP server for the Build phase that renders HTML, Markdown, and URLs to images or PDFs and extracts reader-mode content via Rendex.
What is this MCP server?
- Render HTML, Markdown, or arbitrary URLs to images or PDF
- Reader-mode style content extraction over the Rendex API
- Remote streamable-http MCP at mcp.rendex.dev plus local stdio npm @copperline/rendex-mcp
- Bearer RENDEX_API_KEY from rendex.dev dashboard
- Version 1.4.0; website https://rendex.dev
- Server version 1.4.0
- Dual transport: streamable-http remote and stdio npm package
- Website and API dashboard at rendex.dev
Community signal: 2 GitHub stars.
What problem does it solve?
Agents can write markup and links but struggle to deliver pixel-perfect screenshots, PDFs, and clean article extracts without a dedicated rendering service.
Who is it for?
Builders who already use Rendex and want headless capture and PDF generation inside Claude Code or Cursor threads.
Skip if: Fully offline screenshot needs without API access, or heavy interactive browser automation beyond render and extract.
What do I get? / Deliverables
After you connect RENDEX_API_KEY, your agent can request renders and extractions through MCP instead of manual browser exports or one-off scripts.
- Image or PDF renders from HTML, Markdown, or URLs
- Reader-mode extraction output for research and docs pipelines
Recommended MCP Servers
Journey fit
Screenshot and document rendering supports docs and UI proof artifacts first, which is core Build work before reuse in Launch assets. Docs is the shelf for generating PDFs, captures, and readable exports that document features and onboarding.
How it compares
Rendex-backed render-and-PDF MCP, not a full Playwright skill or design tool.
Common Questions / FAQ
Who is rendex-mcp for?
Indie developers and content-heavy SaaS founders who need programmatic HTML/URL-to-PDF and image renders from MCP-enabled agents.
When should I use rendex-mcp?
Use it when documenting features, prototyping visuals, or preparing launch assets that require consistent renders from HTML, Markdown, or live URLs.
How do I add rendex-mcp to my agent?
Create an API key at rendex.dev, then either point MCP at https://mcp.rendex.dev/mcp with Authorization Bearer or install @copperline/rendex-mcp with RENDEX_API_KEY for stdio.