MCP

ScreenshotOne provides a hosted MCP server that lets compatible AI agents connect to ScreenshotOne securely with OAuth. You do not need to run a local server or copy your ScreenshotOne API key into the MCP client.

Connect to ScreenshotOne MCP

1. Create a ScreenshotOne account, or sign in to your existing account.

2. Follow your client’s setup guide below to add this Streamable HTTP server:

   https://mcp.screenshotone.com

3. Complete ScreenshotOne’s OAuth authorization in the browser, then return to your client.

4. Confirm that the client discovers render-website-screenshot, extract-website-markdown, and get-usage.

Use the root URL exactly as shown, without adding /mcp or /sse. The client must support remote HTTP MCP and OAuth.

Choose your client

Client	Setup guide
Claude	Add a remote custom connector
Claude Code	Add the HTTP server and authenticate
ChatGPT	Create a developer-mode MCP connection
Codex	Configure MCP and sign in
Cursor	Configure mcp.json and connect
VS Code	Add the server and enable its tools
Grok Bot	Connect with Streamable HTTP and OAuth
Hermes Agent	Configure remote MCP with OAuth
OpenClaw	Use native MCP and OAuth
Muse	Connect with Streamable HTTP and OAuth
Another client	Check compatibility and connect

Take and save your first screenshot

After connecting, send this prompt:

Use ScreenshotOne's render-website-screenshot tool to capture
https://example.com with full_page=true. Show me the returned image URL
and download the image as example-screenshot.jpg if you can save files.

The corresponding tool arguments are:

{
    "url": "https://example.com",
    "full_page": true
}

A successful response contains a url. This is an illustration of the response shape, not a working download link:

{
    "url": "https://cache.screenshotone.com/example-screenshot.jpg"
}

Open the actual returned URL to inspect the image. If your client can download files, ask it to save the image and confirm the saved path. Otherwise, open the link in your browser and save it, or download it from a terminal:

curl --fail --location 'PASTE_THE_RETURNED_URL_HERE' --output example-screenshot.jpg

The URL lasts up to four hours. The MCP response contains a link rather than image bytes, so an agent must retrieve the image before it can inspect the pixels. Saving the link alone does not preserve the screenshot.

Start with a public URL. ScreenshotOne renders in its own browser and does not inherit your client’s signed-in browser session. For a long page, add full_page_slices:true so the agent can inspect smaller sections. See the options below.

Available MCP tools

render-website-screenshot

Renders a website screenshot and returns a compact temporary URL instead of embedding the image in the MCP response.

The tool accepts the following options:

• url: The HTTP or HTTPS URL to capture.
• block_banners: Blocks cookie, GDPR, and similar banners and popups. The default is true.
• block_ads: Blocks advertisements. The default is true.
• image_quality: Sets the image quality from 1 to 100. The default is 80.
• full_page: Captures the entire page instead of only the visible viewport. The default is false.
• full_page_slices: Splits a full-page screenshot into smaller vertical images. The default is false and it requires full_page=true.
• metadata_content: Extracts page content with the screenshot and returns it through a temporary URL. The default is false.
• metadata_content_format: Chooses html or markdown for metadata_content. It requires metadata_content=true; the ScreenshotOne API default is html.

These option names and values match the ScreenshotOne API options. ScreenshotOne API response-type and cache controls are not exposed as MCP tool options. The server always requests a JSON response with API caching disabled.

For a screenshot and Markdown content in the same render, use:

{
    "url": "https://example.com",
    "metadata_content": true,
    "metadata_content_format": "markdown"
}

The returned content object contains the temporary Markdown URL and its expiration time. The Markdown is not embedded in the screenshot tool response.

For a long page that an AI agent needs to analyze visually, prefer full_page_slices=true together with full_page=true. Smaller slices are more reliable for agent vision than one unusually tall image.

A call using both features returns:

{
    "url": "https://cache.screenshotone.com/screenshot.jpg",
    "content": {
        "url": "https://cache.screenshotone.com/content.md",
        "expires": "Sun, 07 Sep 2026 12:00:00 GMT",
        "format": "markdown"
    },
    "slices": [
        {
            "index": 0,
            "offset_y": 0,
            "width": 1280,
            "height": 4000,
            "url": "https://cache.screenshotone.com/slice-0.jpg"
        }
    ]
}

The screenshot URL is temporary and is available for up to four hours. Content and slice URLs are also temporary. Download any artifact you need to keep.

extract-website-markdown

Renders a public website and returns its cleaned Markdown directly as MCP text. Use this tool when the agent needs to read, summarize, or extract information from a page without receiving a screenshot.

The tool accepts only one option:

• url: The HTTP or HTTPS URL to extract.

It is a focused shortcut for the ScreenshotOne API’s format=markdown response. No other screenshot or Markdown options are exposed.

get-usage

Returns the ScreenshotOne API quota and concurrency usage for the connected organization. This is useful before an agent starts a larger batch of captures.

See the ScreenshotOne MCP page for supported clients and example workflows.

Local MCP server

If you prefer to run the same screenshot and Markdown tools as a local command-line MCP server, see the ScreenshotOne MCP server on GitHub.

Manage MCP connections

Open the ScreenshotOne Dashboard, go to Integrations, and select Connect MCP clients.

The MCP connections page lists the clients connected to your organization. You can review each connection, rotate its API key, or revoke its access.