get-usage
Returns ScreenshotOne API quota and concurrency usage.
LABSCO 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
USE CASES
01
Seeing what a page actually looks like right now
Render the URL and get the image back in line, without leaving the conversation to open a browser.
02
Capturing a set of pages in one pass
Render each URL in turn, checking usage first so concurrency limits do not cut the run short.
03
Checking where your plan stands
Read the current quota and concurrency figures before committing to a large batch.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
render-website-screenshot
Renders a screenshot and returns an image or cache response.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- SCREENSHOTONE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx --yes @screenshotone/mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"screenshotone": {
"command": "npx",
"args": [
"--yes",
"@screenshotone/mcp"
],
"env": {
"SCREENSHOTONE_API_KEY": "<YOUR_SCREENSHOTONE_API_KEY>"
}
}
}
}
