Integration

ScreenshotRender integration

ScreenshotRender captures a screenshot of any web page in a real browser, with Cloudflare challenges, cookie banners, chat widgets and ads handled by default, and returns a hosted PNG URL together with the page title, meta description and favicon. Capture only the visible viewport or the whole scrollable page. Each successful capture that is not served from the vendor's cache counts against the plan's screenshot quota (the free plan includes 100). Authentication is the API key from the ScreenshotRender dashboard (it starts with sr-), sent as the apiKey query parameter.

Connect ScreenshotRender How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in ScreenshotRender.Built from the 1 ScreenshotRender tool below, on the connection you add once.

What you can do with ScreenshotRender

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

capture_screenshotCapture screenshotGETAgents: ask firstCaptures a web page and returns data.screenshot (a hosted PNG URL) plus the page title, description and favicon. Billed: each successful capture not served from the vendor's cache uses one screenshot of the plan quota.

Use ScreenshotRender from Claude Code, Cursor or Codex

Connect ScreenshotRender in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ScreenshotRender operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect ScreenshotRender

Create your workspace
Sign up free. Nothing to install.
Connect ScreenshotRender once
Add your ScreenshotRender connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.