mcpField
U
Urlbox Full Page Screenshots

Urlbox Full Page Screenshots

Local
github.com/urlboxBrowser Automation3Updated 2w ago

About Urlbox Full Page Screenshots

An MCP server for the Urlbox Screenshot API, intended for AI clients that need to capture or inspect websites. It handles screenshots, PDFs, videos, and text extraction, while its local bridge can save rendered files to the computer.

Key features

  1. 01Create website screenshots, PDFs, and videos
  2. 02Extract HTML, Markdown, and article text
  3. 03Compare pages and manage projects and webhooks
  4. 04Check usage
  5. 05Save rendered files locally

Use cases

  1. 01Create a screenshot or PDF of a webpage
  2. 02Convert an article into Markdown
  3. 03Inspect how a page appears on a phone

MCP support

It provides Urlbox tools to MCP clients through a hosted endpoint or a local stdio bridge. Tools cover rendering, content extraction, and project, webhook, and usage management; the local bridge also adds a tool for saving rendered files.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Urlbox Screenshot MCP Server

image

Give your AI assistant a real browser for website screenshots. The Urlbox MCP server takes screenshots, makes PDFs and videos, extracts HTML, markdown and article text, compares pages, and manages your Urlbox projects, webhooks and usage.

Use the hosted server (recommended)

Connect your client to https://api.urlbox.com/mcp. Nothing to install.

  • Claude (claude.ai and desktop): Settings, Connectors, Add custom connector, enter https://api.urlbox.com/mcp, then sign in to Urlbox.

  • ChatGPT: add a connector with the URL https://api.urlbox.com/mcp, then sign in to Urlbox.

  • Claude Code: claude mcp add --transport http urlbox https://api.urlbox.com/mcp, then run /mcp to sign in.

  • Codex: codex mcp add urlbox --url https://api.urlbox.com/mcp, then codex mcp login urlbox to sign in.

  • Cursor: add this to ~/.cursor/mcp.json:

    {
      "mcpServers": {
        "urlbox": {
          "url": "https://api.urlbox.com/mcp",
          "headers": { "Authorization": "Bearer YOUR_URLBOX_API_KEY" }
        }
      }
    }
    

Clients that can't sign in can send an API key as Authorization: Bearer <key>. An organisation API key (ubx_org_...) unlocks every tool. A project secret key works for the rendering tools only. Find your keys in the Urlbox dashboard.

Local bridge (this package)

Some clients can only start local servers. This package is a small local bridge: it runs on your machine over stdio and forwards everything to the hosted server, so you get exactly the same tools, always up to date.

{
  "mcpServers": {
    "urlbox": {
      "command": "npx",
      "args": ["-y", "@urlbox/screenshot-mcp"],
      "env": {
        "URLBOX_API_KEY": "your_api_key_here"
      }
    }
  }
}

Requires Node.js 20 or later.

VariableDescription
URLBOX_API_KEYYour organisation API key or project secret key.
SECRET_KEYAlso accepted, for configs written for 1.x. URLBOX_API_KEY wins if both are set.
URLBOX_DOWNLOAD_DIRWhere save_render saves files. Defaults to ~/Downloads.

The bridge adds one local tool, save_render, which downloads a render URL returned by any Urlbox tool and saves it to your computer. Just ask, for example "screenshot example.com and save it to my computer". Existing files are never overwritten.

Upgrading from 1.x

Your existing config keeps working: SECRET_KEY is still read and the package name and command are unchanged.

  • Tools now come from the hosted server, so there are many more of them, and they keep improving without an update.
  • render is still there. Its store_renders option and the download tool are replaced by save_render.
  • Files are saved to ~/Downloads instead of ~/Downloads/urlbox-renders. Set URLBOX_DOWNLOAD_DIR to keep the old location.
  • With a project secret key you get the rendering tools. Use an organisation API key to also manage projects, webhooks and usage.
  • Node.js 20 or later is required.

Example prompts

Development

npm install
npm test

The tests run the bridge against a local fake server, so they need no Urlbox account.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.