Other MCP clients

Your client must support remote Streamable HTTP MCP servers and OAuth authorization. A client with only local stdio support needs a compatible bridge or the separate local ScreenshotOne MCP server.

Connect

1. Create a ScreenshotOne account.
2. Add https://mcp.screenshotone.com as a remote HTTP MCP server. Use the root URL exactly; do not append /mcp or /sse.
3. Follow your client’s OAuth login action. Sign in to ScreenshotOne in the browser and approve the connection.
4. Confirm discovery of render-website-screenshot, extract-website-markdown, and get-usage.

Configuration keys vary by client. Use its remote-server configuration format rather than copying a local command entry or another client’s JSON wrapper.

Test the connection

Ask the client to call render-website-screenshot with these arguments:

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

Expect a temporary image url. Open or download it to check the rendered result. The MCP response does not embed the screenshot bytes, and receiving the URL does not save a file. See the capture and save walkthrough.

If it fails

Check transport support, OAuth support, the exact endpoint, and whether the client has enabled the discovered tools. If it asks for a static API key and offers no OAuth flow, this hosted setup may not be supported by that client.

Review tool options and manage existing connections.