Summary
Screenshot rendering as a single call, from the vendor that runs the renderer.
The whole surface is one rendering tool plus a usage read, which is the right shape for this job: you hand it a URL and get the image back in the conversation. The usage tool matters more than it looks — quota and concurrency are what stop a batch of captures halfway through.
What it is
ScreenshotOne's own server: two tools over its rendering API, one that takes the screenshot and one that reports usage.
What you get
- A rendered screenshot of any URL, returned as an image or as a cached response
- Your current ScreenshotOne quota and concurrency usage
Requirements
A ScreenshotOne API key, passed as SCREENSHOTONE_API_KEY. Runs from npm as @screenshotone/mcp over stdio; ScreenshotOne also operates a hosted MCP server if you would rather not run this one yourself.
Setup effort
One command plus a key — npx --yes @screenshotone/mcp, then supply credentials