Urlbox

io.github.urlboxPublished by GitHub account urlboxv2.0.0Updated Oct 24, 2026

Screenshots, PDFs, video, markdown and page data from any website, via Urlbox.

The publisher's own server: screenshot.com.ar

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser AutomationFiles & Storage

Overview

AI-generated overview

Urlbox gives an assistant a hosted browser to screenshot, PDF, video, markdown and extract data from any website, with an optional local bridge for saving files

What you can do
Capture screenshots, PDFs and videos of web pages, including mobile views and ad or cookie-banner removal. Extract HTML, markdown and article text from a page. Compare pages and read page data. Manage Urlbox projects, webhooks and usage with an organisation key. Save a returned render to the local machine through the bridge's save_render tool.
When to use it
Useful when you need visual captures or clean text from live websites, such as documenting a page, turning an article into markdown, checking a mobile layout, or archiving a page as PDF. Choose the hosted endpoint for the full tool set; use the local bridge only if your client can start only local servers.
Requirements
Either the hosted endpoint at api.urlbox.com/mcp with OAuth sign-in, or the npm package run with npx, which needs Node.js 20 or later. A Urlbox account and key: URLBOX_API_KEY (organisation key for all tools, project secret key for rendering only), or an Authorization Bearer header. URLBOX_DOWNLOAD_DIR optionally sets where save_render writes, defaulting to ~/Downloads.
Before you install
The API key is a secret sent to Urlbox; keep it out of shared configs. Renders and page data are processed by Urlbox's hosted service, so page content leaves your machine. The bridge writes files to disk, though existing files are never overwritten. Organisation keys also allow managing projects and webhooks, which changes account state.

Installation

In SourceWeft

  1. Open Urlbox in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.urlbox%2Fscreenshot-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "urlbox": {
      "type": "http",
      "url": "https://api.urlbox.com/mcp"
    }
  }
}

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:

    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.

json
{  "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

bash
npm installnpm test

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

License

MIT

Source: README.md at commit bd4715e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestOct 13, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Screenshot integrations