Urlbox MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SECRET_KEY | Yes | Your Urlbox API Secret Key, obtained from the Urlbox dashboard. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| renderB | Uses Urlbox.com's POST API for advanced rendering with side renders. Download to computer using store_renders: true. Ideal for: use of many options, converting websites to HTML/PDF/markdown, extracting metadata, saving cookies, rendering custom HTML/CSS/JS, and generating multiple output formats simultaneously (html, pdf, md, cookies etc.), while also capturing the main screenshot's format. |
| downloadC | Takes all of the render URLs from any Urlbox response that hasn't already been downloaded, and saves it to the users file system. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools, download and render, have clearly distinct purposes: one for rendering websites with advanced options, the other for downloading render URLs to the file system. No ambiguity.
Both tool names are single verbs (download, render), which is consistent within the set. While not following a typical verb_noun pattern, they are uniformly imperative and predictable.
With only 2 tools, the server feels minimal for its stated purpose of website rendering and file downloading. It covers primary actions but lacks supporting tools like listing or deleting renders, making it slightly thin.
The core workflow of rendering and downloading is covered, but there are notable gaps such as status checking, authentication, or render management. The inclusion of download as a separate tool is useful, but overall the surface is incomplete for a full rendering service.