OpenClaw
Screenshots and Markdown MCP server for OpenClaw
These instructions use a current OpenClaw release with the native openclaw mcp commands. Have a ScreenshotOne account ready.
Configure the server
Section titled “Configure the server”Run:
openclaw mcp set screenshotone '{"url":"https://mcp.screenshotone.com","transport":"streamable-http","auth":"oauth"}'openclaw mcp login screenshotoneComplete ScreenshotOne’s OAuth authorization in the browser, then return to the terminal. Explicitly select streamable-http; an SSE configuration is a different transport.
Check authorization with:
openclaw mcp status --verboseThis uses OpenClaw’s shared operator OAuth connection. Agents using that connection act through the authorized ScreenshotOne account. For separate accounts per requester, consult OpenClaw’s transports and OAuth guide.
Take and save a screenshot
Section titled “Take and save a screenshot”Use ScreenshotOne's render-website-screenshot tool to capturehttps://example.com with full_page=true. Download the returned imageURL and save a copy with the results of this task.The tool returns a temporary url. Confirm that your agent actually downloads the image if you need a persistent attachment; a stored link will expire within four hours.
If the server is not available
Section titled “If the server is not available”If openclaw mcp is not recognized, check your OpenClaw version against its MCP CLI reference. If status reports authorization-required, repeat the login command. For a stuck connection, run openclaw mcp logout screenshotone and then log in again.
This configuration is separate from the API-key-based ScreenshotOne skill for OpenClaw. See MCP tool options and manage the OAuth connection.