Rendex: Rendering API for Images, PDFs & Content Extraction MCP Server

by copperline-labs Your server? Claim it

answering

Rendex: Rendering API for Images, PDFs & Content Extraction is answering right now. Last checked 13 min ago. 54 installs a week from npm. It exposes 13 tools. Last commit 14 Aug 2026.

Render HTML, Markdown, or URLs to images, PDF, or branded artifacts; extract and watch pages.

Installs per day peak 27 · avg 9 · +64% w/w

a month agotoday

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

215 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 August 2026. No other catalogue keeps this.

14 Aug 2 tools changed the parameters they ask for watch_create, watch_test

Nothing serious here today

Today is the operative word: we check Rendex: Rendering API for Images, PDFs & Content Extraction every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add rendex-mcp --transport http https://mcp.rendex.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rendex-mcp": {
      "url": "https://mcp.rendex.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.rendex-mcp]
url = "https://mcp.rendex.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "rendex-mcp": {
      "url": "https://mcp.rendex.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "rendex-mcp": {
      "url": "https://mcp.rendex.dev/mcp"
    }
  }
}

This one needs environment variables set before it will start: RENDEX_API_KEY (API key from rendex.dev dashboard). The author declared them in the registry entry; get the values from the project itself.

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

watch

watch_create

Use this when the user asks to monitor, watch, or track a webpage for changes, or to be alerted/notified when a page changes. Do NOT use for a one-time capture (use rendex_screenshot). Creates a Rendex Watch — monitors a URL on a schedule and notifies when it changes (real-Chrome visual diff with a highlighted overlay, an extracted-text diff, or both). An active watch captures its baseline immediately. Returns the created watch as JSON.

watch_delete

Delete a watch and its run history. Irreversible.

watch_get

Fetch one watch by ID, including its current baseline image URL and status. Returns JSON.

watch_list

List your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }.

watch_run

Run an immediate check now (charges 1 credit). Returns the queued run; poll watch_runs for the result or receive a watch.changed webhook.

watch_runs

Read a watch's run history (newest first), paged. Each run includes changed, diffScore, and signed before/after/overlay image URLs. Returns { items, nextCursor }.

watch_test

Dry-run a watch config BEFORE creating it — render the proposed config once and report what was captured + whether the page is reachable (and the text a text-watch would compare). Creates no watch, no baseline, no diff. Use this to validate a selector/scope/identity first. Returns JSON.

watch_update

Update a watch in place — pause/resume (paused), re-point (url), change schedule/diff/notify settings, or turn a channel off (webhookUrl/notifyEmail = null). Only the fields you send change; renderParams is deep-merged over the existing config. A scope change (url/selector/fullPage/size/device) re-baselines on the next check. Returns the updated watch as JSON.

rendex

rendex_account

Check the Rendex account: which plan it's on, how many render credits have been used vs. the monthly limit (and when it resets), the per-minute rate limit, and a one-tap link to upgrade to a higher tier. Use this whenever the user asks about their usage, remaining quota, current plan, or how to get more renders / stop hitting limits. Read-only — costs no credits.

rendex_extract

Use this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL. Do NOT use for a visual screenshot (use rendex_screenshot). Extracts 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 — handles SPAs that fetch-only readers miss. Strips nav, ads, and boilerplate, returning the article body plus title, byline, and excerpt. Great for feeding page content to an LLM, summarization, or RAG ingestion. Costs 1 render credit per call.

rendex_render_link

Use this when the user wants a reusable, HOSTED image URL — an og:image or a link to embed in an <img> tag — rather than the image bytes. Do NOT use for a one-off inline screenshot (use rendex_screenshot). Renders a URL, raw HTML, or Markdown and gives 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 <img> tag and Rendex serves a cached copy on every share. Takes the same options as rendex_screenshot, plus an optional expiresIn. Returns { url, expiresAt, format, cacheTtl } as JSON. Costs 1 render credit per fresh render; cached repeat hits don't re-charge.

rendex_screenshot

Use this when the user asks to screenshot, capture, or take a picture of a webpage/URL, or to render raw HTML or Markdown to an image or PDF. Do NOT use to get a reusable hosted image URL (use rendex_render_link) or to make a branded multi-format document (use render_artifact). Captures a screenshot or PDF of any webpage, raw HTML, or Markdown. Supports full-page capture, dark mode, ad blocking, custom viewports, CSS/JS injection, cookie/header injection, PDF output, HTML and Markdown rendering, and progressive fallback for heavy sites. Returns partial renders on timeout by default (bestAttempt mode). Costs 1 render credit per call. Cookie/header injection requires Starter+; geo-targeting requires Pro+.

render

render_artifact

Use this when the user asks to make or create a branded report, invoice, summary, release notes, or document — or to 'turn this Markdown/HTML into a PDF and PNG' (optionally with a logo or accent color). Do NOT use to screenshot an existing URL (use rendex_screenshot). Turns Markdown or HTML into a branded, downloadable artifact — a PDF, a PNG, and a hosted share page — in one call. Apply a logo, accentColor, font, header, and footer. Returns hosted URLs { pdfUrl, pngUrl, shareUrl, expiresAt }. Each requested format costs 1 render credit.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.rendex.dev/mcp	streamable-http	answering	230 ms	13 min ago

Alternatives to Rendex: Rendering API for Images, PDFs & Content Extraction

same job, measured the same way

Snaprender

by user0856

Screenshot, extract content, and render web pages. PNG/JPEG/WebP/PDF, batch, signed URLs.

46 installs/wk local only

Skillforge Render API

by skillforge99

Screenshot, PDF, OG-image, and page extraction (markdown/JSON) over MCP. Bearer key or x402.

4 tools answering

MarkGrab

by arknill

Universal web content extraction — any URL to LLM-ready markdown. HTML, YouTube, PDF, DOCX.

104 installs/wk local only

PDF Text, Table and OCR Extractor

by brenton-keller

PDF URLs to per-page text, tables as rows, Markdown, metadata and OCR for scanned pages.

answering

markitai

by ynewtime

Convert documents, images and web pages to clean Markdown, for agents: single, URL and batch tools.

local only

OCR

by pennyocr

Read PDFs and images as markdown or text, with exact costs and hard spend caps. $0.75/1k pages.

2 tools answering

Propzapi

by paperandbeyond23-gif

Render-and-verify API: HTML/CSS to image or PDF, screenshot any URL, confirm the text rendered.

3 tools answering

MCP Document Converter

by xt765

Convert PDF, DOCX, HTML, Markdown, and Text for AI assistant context injection.

98 installs/wk local only

Rendex: Rendering API for Images, PDFs & Content Extraction — questions

Answers built from our own checks of this server.

What can Rendex: Rendering API for Images, PDFs & Content Extraction do?

It exposes 13 tools, read directly from the server on our last check. Among them: render_artifact, rendex_account, rendex_extract, rendex_render_link, rendex_screenshot, watch_create and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Rendex: Rendering API for Images, PDFs & Content Extraction mostly used for?

Its tools cluster around watch and rendex. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Rendex: Rendering API for Images, PDFs & Content Extraction working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 215 ms. The bar chart above shows every period we have measured.

How do I connect Rendex: Rendering API for Images, PDFs & Content Extraction?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Rendex: Rendering API for Images, PDFs & Content Extraction need an API key?

No. Rendex: Rendering API for Images, PDFs & Content Extraction completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Rendex: Rendering API for Images, PDFs & Content Extraction?

It answers our handshake in 215 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Rendex: Rendering API for Images, PDFs & Content Extraction?

The npm package @copperline/rendex-mcp was installed 54 times in the last week. Week over week that is +64%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Rendex: Rendering API for Images, PDFs & Content Extraction open source?

Yes — it is published under the MIT licence, written in TypeScript and 7 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.