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.

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:

1
{
2
    "url": "https://example.com",
3
    "metadata_content": true,
4
    "metadata_content_format": "markdown"
5
}

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:

1
{
2
    "url": "https://cache.screenshotone.com/screenshot.jpg",
3
    "content": {
4
        "url": "https://cache.screenshotone.com/content.md",
5
        "expires": "Sun, 07 Sep 2026 12:00:00 GMT",
6
        "format": "markdown"
7
    },
8
    "slices": [
9
        {
10
            "index": 0,
11
            "offset_y": 0,
12
            "width": 1280,
13
            "height": 4000,
14
            "url": "https://cache.screenshotone.com/slice-0.jpg"
15
        }
16
    ]
17
}

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 integration page for the hosted server URL, local server option, and related resources.

Connect to ScreenshotOne MCP

Open the MCP settings in your AI agent or MCP client.
Add the following URL as a remote MCP server:
```
1
https://mcp.screenshotone.com
```
Sign in to ScreenshotOne in the browser and approve the connection.
Return to your agent and start using ScreenshotOne.

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.