Integration

UrlBox integration

UrlBox is a screenshot API service that captures full-page website screenshots, PDFs, and videos. It supports advanced options like element selection, viewport customization, and dynamic content rendering with JavaScript.

Connect UrlBox How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in UrlBox.Built from the 6 UrlBox tools below, on the connection you add once.

Common UrlBox use cases

Record animated content
Generate invoices as PDF
Poll for render completion
Batch screenshot processing
Capture specific components
Capture website screenshots
Screenshot widgets
Non-blocking captures
Check async job status
Convert reports to PDF

What you can do with UrlBox

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.

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

Screenshot, 3 operations

render_asyncRender asyncPOSTCreate screenshot asynchronously
render_elementRender elementPOSTScreenshot specific element
render_syncRender syncPOSTCreate screenshot synchronously

Pdf, 1 operation

render_pdfRender pdfPOSTGenerate PDF from URL

Render, 1 operation

get_render_statusGet render statusGETGet render status

Video, 1 operation

render_videoRender videoPOSTRecord webpage video

UrlBox API rate limits

Rate limits vary by plan. Concurrent render limits apply.

These are the limits UrlBox documents, not ones LiveContext measured. They can change and often depend on your plan, so check the UrlBox documentation for current values.

Use UrlBox from Claude Code, Cursor or Codex

Connect UrlBox in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its UrlBox 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 UrlBox

Create your workspace
Sign up free. Nothing to install.
Connect UrlBox once
Add your UrlBox 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.

UrlBox integration FAQ

What can you do with the UrlBox integration?

LiveContext exposes 6 operations on UrlBox, covering screenshot, pdf, render and video. Common uses include Record animated content, Generate invoices as PDF and Poll for render completion.

What are the UrlBox API rate limits?

Rate limits vary by plan. Concurrent render limits apply. Limits are set by UrlBox and can depend on your plan.