rendex-mcp
@copperline/rendex-mcp
MCP-сервер для Rendex — создание скриншотов и PDF-файлов любых веб-страниц с помощью ИИ-агентов через протокол Model Context Protocol.
Быстрый старт
Claude Desktop / Cursor / Windsurf (npx)
Добавьте в конфигурацию вашего MCP-клиента:
{
"mcpServers": {
"rendex": {
"command": "npx",
"args": ["-y", "@copperline/rendex-mcp"],
"env": {
"RENDEX_API_KEY": "your-api-key"
}
}
}
}Где добавить:
Клиент | Расположение конфигурации |
Claude Desktop |
|
Cursor |
|
Windsurf | Настройки > MCP Servers |
Claude Code (CLI)
Добавьте .mcp.json в корень вашего проекта с той же конфигурацией, что указана выше. Затем перезапустите Claude Code.
Важно: Добавьте
.mcp.jsonв ваш.gitignore— он содержит ваш API-ключ.
Удаленно (без установки)
Подключайтесь напрямую — установка не требуется (только для Claude Desktop):
{
"mcpServers": {
"rendex": {
"url": "https://mcp.rendex.dev/mcp",
"headers": {
"Authorization": "Bearer your-api-key"
}
}
}
}Related MCP server: Screenshot API
Инструменты
rendex_screenshot
Создание скриншота или PDF-файла любой веб-страницы или необработанного HTML.
"Take a screenshot of https://example.com"
"Capture the full page of https://news.ycombinator.com in dark mode"
"Generate a PDF of https://github.com with A4 page size"
"Capture https://amazon.de as seen from Germany"
"Render this HTML invoice as a PDF"Параметры:
Параметр | Тип | По умолчанию | Описание | |||
| string | обязателен* | URL веб-страницы для захвата. Взаимоисключающий с | |||
| string | — | Необработанный HTML для рендеринга. Взаимоисключающий с | |||
|
|
|
|
|
| Формат вывода |
| boolean |
| Захват всей прокручиваемой страницы | |||
| boolean |
| Эмуляция темной цветовой схемы | |||
| number |
| Ширина области просмотра (320-3840) | |||
| number |
| Высота области просмотра (240-2160) | |||
| number |
| Качество изображения 1-100 (только для JPEG/WebP, по умолчанию 80) | |||
| number |
| Задержка в мс перед захватом | |||
| boolean |
| Блокировка рекламы и трекеров | |||
| string[] | — | Типы блокируемых ресурсов: | |||
| number |
| Коэффициент масштабирования устройства (1-3). По умолчанию 2× Retina | |||
| number |
| Максимальное время ожидания загрузки страницы в секундах (5-60) | |||
| string |
| Готовность страницы: | |||
| string | — | CSS-селектор, который нужно дождаться перед захватом | |||
| boolean |
| Возвращать частичный рендер при тайм-ауте вместо ошибки | |||
| string | — | CSS-селектор элемента для захвата вместо всей страницы | |||
| string | — | Пользовательский CSS для внедрения перед захватом (макс. 50 КБ) | |||
| string | — | Пользовательский JavaScript для выполнения перед захватом (макс. 50 КБ) | |||
| array | — | Файлы cookie для аутентифицированных захватов (макс. 50) | |||
| object | — | Пользовательские HTTP-заголовки для запроса страницы | |||
| string | — | Переопределение строки user agent браузера | |||
| string | — | Размер страницы PDF: | |||
| boolean | — | Альбомная ориентация PDF | |||
| boolean |
| Печать фона в PDF | |||
| number |
| Коэффициент масштабирования PDF (0.1-2) | |||
| object | — | Поля PDF: | |||
| string | — | Код страны ISO для геотаргетированного захвата (Pro/Enterprise) | |||
| string | — | Город для геотаргетинга (требуется | |||
| string | — | Штат для геотаргетинга (требуется | |||
| boolean | — | Обработка асинхронно (возвращает ID задания) | |||
| string | — | URL для получения обратного вызова при завершении асинхронного захвата | |||
| number | — | Время кэширования результата в секундах (3600-2592000) |
Аутентификация
Получите ваш API-ключ на rendex.dev.
Установите переменную окружения RENDEX_API_KEY в конфигурации вашего MCP-клиента.
Тарифы
План | Запросов/мес | Скорость |
Free | 500 | 10/мин |
Starter | 10,000 | 60/мин |
Pro | 100,000 | 300/мин |
Enterprise | Пользовательский | 1,000/мин |
Лицензия
MIT — Copperline Labs LLC
Available Tools
11 toolsrendex_extractAInspect
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 — 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.
Inputs: url (required), extractFormat, waitUntil, timeout, +4 more.
rendex_render_linkAInspect
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 or an 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.
Inputs: url, html, markdown, format, +37 more.
rendex_screenshotAInspect
Capture 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).
Inputs: url, html, markdown, format, +36 more.
watch_createBInspect
Create a Rendex Watch — monitor a URL on a schedule and get notified 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.
Inputs: url (required), name, intervalMinutes, diffMode, +6 more.
watch_deleteAInspect
Delete a watch and its run history. Irreversible.
Inputs: id (required).
watch_getAInspect
Fetch one watch by ID, including its current baseline image URL and status. Returns JSON.
Inputs: id (required).
watch_listAInspect
List your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }.
Inputs: status, cursor, limit.
watch_runAInspect
Run an immediate check now (charges 1 credit). Returns the queued run; poll watch_runs for the result or receive a watch.changed webhook.
Inputs: id (required).
watch_runsAInspect
Read a watch's run history (newest first), paged. Each run includes changed, diffScore, and signed before/after/overlay image URLs. Returns { items, nextCursor }.
Inputs: id (required), cursor, limit.
watch_testAInspect
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.
Inputs: url (required), name, intervalMinutes, diffMode, +6 more.
watch_updateAInspect
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.
Inputs: id (required), url, name, intervalMinutes, +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
The two tool families are clearly separated (rendering vs. watch management), and each watch operation has a distinct role. However, rendex_screenshot and rendex_render_link share nearly the same rendering pipeline and options, and watch_run vs. watch_runs differ by only one letter, so a couple of tools could still be misselected without careful reading.
All tool names use snake_case and a recognizable family prefix: rendex_* for rendering and watch_* for watch management. The imperative verb pattern is mostly consistent within the watch family, though watch_runs is a noun rather than a verb and rendex_screenshot reads as a noun, creating minor inconsistency.
At 11 tools, the surface is well-scoped and reasonable for the server's dual purpose: three rendering/capture tools and eight watch lifecycle tools. Each tool has a clear job, and none feel redundant or unnecessary.
The watch family is fully fleshed out with create, read, list, update, delete, test, run, and history operations. The rendering family covers capture, extraction, and hosted-link generation, which covers the apparent domain without obvious dead ends.
Maintenance
Related MCP Connectors
Screenshot, PDF and Open Graph image API for AI agents: capture pages, render PDFs, make OG images.
Screenshot API for AI agents. Any public page as image or PDF, banners hidden, 227 countries.
Generate images, GIFs, videos, and PDFs from HTML, URLs, or templates — from your AI agent.
Generate images and PDFs from HTML/CSS, live websites, and reusable templates.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to generate images from HTML/CSS, capture URL screenshots, and manage reusable templates through the RendShot API. Provides tools for rendering visual content programmatically within AI workflows.13 npm-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to capture any public URL as PNG, JPEG, or PDF via REST API or MCP tools, including screenshot capture, page description, and PDF rendering.18 npmMIT
- AlicenseNot gradedqualityDmaintenanceHosted, SSRF-safe, cached screenshots and Open Graph images for AI agents - no headless Chrome to run.46 npmMIT
- AlicenseAqualityCmaintenanceScreenshot, visual-diff, and AI page-analysis API for AI agents. Capture any URL as PNG, JPEG, WebP, PDF, or HTML, diff two versions of a page to catch visual regressions, and get an AI summary of what a page contains.362 npm1MIT