Rendex 用のMCPサーバー — Model Context Protocolを使用して、AIエージェント経由であらゆるWebページのスクリーンショットやPDFをキャプチャします。
MCPクライアントの設定に追加してください：
{
"mcpServers": {
"rendex": {
"command": "npx",
"args": ["-y", "@copperline/rendex-mcp"],
"env": {
"RENDEX_API_KEY": "your-api-key"
}
}
}
}追加場所:
クライアント | 設定ファイルの場所 |
Claude Desktop |
|
Cursor | プロジェクトルートの |
Windsurf | 「設定」>「MCP Servers」 |
プロジェクトルートに上記と同じ設定で .mcp.json を追加します。その後、Claude Codeを再起動してください。
重要:
.mcp.jsonにはAPIキーが含まれているため、.gitignoreに追加してください。
直接接続します（インストール不要、Claude Desktopのみ）:
{
"mcpServers": {
"rendex": {
"url": "https://mcp.rendex.dev/mcp",
"headers": {
"Authorization": "Bearer your-api-key"
}
}
}
}Related MCP server: Screenshot API
rendex_screenshotあらゆるWebページや生のHTMLのスクリーンショットまたはPDFをキャプチャします。
"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 | 必須* | キャプチャするWebページのURL。 | |||
| string | — | レンダリングする生のHTML。 | |||
|
|
|
|
|
| 出力フォーマット |
| boolean |
| スクロール可能なページ全体をキャプチャ | |||
| boolean |
| ダークモードの配色をエミュレート | |||
| number |
| ビューポートの幅 (320-3840) | |||
| number |
| ビューポートの高さ (240-2160) | |||
| number |
| 画像品質 1-100 (JPEG/WebPのみ、デフォルト80) | |||
| number |
| キャプチャ前の待機時間 (ms) | |||
| boolean |
| 広告とトラッカーをブロック | |||
| string[] | — | ブロックするリソースタイプ: | |||
| number |
| デバイスのピクセル比 (1-3)。デフォルトは2× Retina | |||
| number |
| ページ読み込みの最大待機時間 (秒) (5-60) | |||
| string |
| ページの準備完了状態: | |||
| string | — | キャプチャ前に待機するCSSセレクタ | |||
| boolean |
| タイムアウト時に失敗せず、部分的なレンダリングを返す | |||
| string | — | ページ全体ではなく、キャプチャする要素のCSSセレクタ | |||
| string | — | キャプチャ前に注入するカスタムCSS (最大50KB) | |||
| string | — | キャプチャ前に実行するカスタムJavaScript (最大50KB) | |||
| array | — | 認証済みキャプチャ用に設定するCookie (最大50個) | |||
| object | — | ページリクエスト用のカスタムHTTPヘッダー | |||
| string | — | ブラウザのユーザーエージェント文字列を上書き | |||
| string | — | PDFのページサイズ: | |||
| boolean | — | PDFの横向き設定 | |||
| boolean |
| PDFで背景を印刷 | |||
| number |
| PDFのスケール倍率 (0.1-2) | |||
| object | — | PDFの余白: CSS値として | |||
| string | — | ジオターゲティングキャプチャ用のISO国コード (Pro/Enterprise) | |||
| string | — | ジオターゲティング用の都市名 ( | |||
| string | — | ジオターゲティング用の州名 ( | |||
| boolean | — | 非同期処理 (ジョブIDを返す) | |||
| string | — | 非同期キャプチャ完了時にコールバックを受け取るURL | |||
| number | — | 結果をキャッシュする秒数 (3600-2592000) |
rendex.dev でAPIキーを取得してください。
MCPクライアントの設定で RENDEX_API_KEY 環境変数を設定してください。
プラン | 月間コール数 | レート |
Free | 500 | 10/分 |
Starter | 10,000 | 60/分 |
Pro | 100,000 | 300/分 |
Enterprise | カスタム | 1,000/分 |
MIT — Copperline Labs LLC
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.
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.
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.
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.
Delete a watch and its run history. Irreversible.
Inputs: id (required).
Fetch one watch by ID, including its current baseline image URL and status. Returns JSON.
Inputs: id (required).
List your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }.
Inputs: status, cursor, limit.
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).
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
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.
