Enterprise DNA
M MCP Servers Developer low

copperline-labs/rendex-mcp

by Various

MCP server for Rendex — capture screenshots, generate PDFs, and render HTML to images of any webpage via AI agents. Claude, Cursor, Windsurf compatible.

C

MCP

copperline-labs/rendex-mcp

Added 1 June 2026

#ai-agent #api #claude #cloudflare-workers #mcp #mcp-server #model-context-protocol #rendex

Overview

An MCP server that lets AI agents capture screenshots, generate PDFs, and render HTML to images from any webpage. It works with Claude, Cursor, and Windsurf by exposing Rendex capabilities through the Model Context Protocol.

Best for

Best for
Developers building AI agents that need visual webpage capture or PDF generation

Use cases

  • Capture full-page screenshots of webpages via AI agent commands
  • Generate PDFs from live URLs or HTML content programmatically
  • Render HTML to image for visual verification in agent workflows

Notes

An MCP server that lets AI agents capture screenshots, generate PDFs, and render HTML to images from any webpage. It works with Claude, Cursor, and Windsurf by exposing Rendex capabilities through the Model Context Protocol.

2 stars on GitHub. Last updated 2026-05-31. Licensed MIT.

Use cases

  • Capture full-page screenshots of webpages via AI agent commands
  • Generate PDFs from live URLs or HTML content programmatically
  • Render HTML to image for visual verification in agent workflows

Pros

  • Works with multiple popular AI agent platforms out of the box
  • Simple MCP integration for existing agent setups
  • Handles both URL-based and raw HTML input

Cons

  • Very early stage with only 2 GitHub stars and limited community adoption
  • No documented error handling or rate limiting for production use
  • Dependency on Rendex service availability and performance

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Works with multiple popular AI agent platforms out of the box
  • Simple MCP integration for existing agent setups
  • Handles both URL-based and raw HTML input

Cons

  • Very early stage with only 2 GitHub stars and limited community adoption
  • No documented error handling or rate limiting for production use
  • Dependency on Rendex service availability and performance