Urlbox MCP Server is a browser tool server for AI assistants that can take screenshots of websites, generate PDFs and videos, extract HTML, Markdown, and article body text, compare pages, and manage Urlbox projects, webhooks, and usage.
[Purpose] Provide real browser capabilities for Claude, ChatGPT, and other AI assistants, allowing assistants to directly fetch and render web content and return the results as screenshots, PDFs, videos, or text.
[Main capabilities]
- Website screenshots
- Generate PDFs
- Generate videos
- Extract HTML, Markdown, and article body text
- Compare pages
- Manage Urlbox projects, webhooks, and usage
[Usage] Using the hosted server is recommended; connect the client to https://api.urlbox.com/mcp with no installation required. The configuration for different clients is as follows:
Claude (claude.ai and desktop): In Settings, Connectors, Add custom connector, enter https://api.urlbox.com/mcp , then log in to Urlbox.
ChatGPT: Add a connector with the URL https://api.urlbox.com/mcp , then log in to Urlbox.
Claude Code: Run claude mcp add --transport http urlbox https://api.urlbox.com/mcp , then run /mcp to log in.
Codex: Run codex mcp add urlbox --url https://api.urlbox.com/mcp , then run codex mcp login urlbox to log in.
Cursor: Add the following to ~/.cursor/mcp.json: { "mcpServers" : { "urlbox" : { "url" : " https://api.urlbox.com/mcp " , "headers" : { "Authorization" : " Bearer YOUR_URLBOX_API_KEY " } } } }
Clients that cannot log in can send an API key via Authorization: Bearer <key>. Organization API keys (ubx_org_...) unlock all tools; project keys only work with rendering tools. Keys can be found in the Urlbox dashboard.
[Local bridge] Some clients can only start local servers. This package is a small local bridge that runs over stdio on the user's machine and forwards all requests to the hosted server, so the tools are exactly the same as the hosted server and always up to date. Node.js 20 or later is required.
The bridge additionally adds a local tool, save_render, for downloading the render URL returned by any Urlbox tool and saving it to the computer. For example, you can ask "take a screenshot of example.com and save it to my computer." Existing files will not be overwritten.
Upgrading from 1.x: Existing configurations continue to work, SECRET_KEY is still read, and the package name and command remain unchanged. Tools now come from the hosted server, so there are more of them and they continue to improve without updates. render still exists, and its store_renders option and download tool are replaced by save_render. Files are saved to ~/Downloads instead of ~/Downloads/urlbox-renders; you can set URLBOX_DOWNLOAD_DIR to keep the old location. With a project key, you only get rendering tools; with an organization API key, you can also manage projects, webhooks, and usage. Node.js 20 or later is required.
[Example prompt]
- Take a screenshot of https://example.com without ads or cookie banners.
- Save https://urlbox.com as a tagged PDF with an outline and download it to my computer.
- Turn this article into markdown: https://example.com/blog/post
- How does https://example.com look on a phone?
[Limitations] Using the rendering tools requires a Urlbox API key; managing projects, webhooks, and usage requires an organization API key. The local bridge method requires Node.js 20 or later. Tests run the bridge through a local fake server, so no Urlbox account is required.
