Summary
Returning both the inline image and a hosted URL covers the two things you do with a screenshot, and most services give you one.
Inline means the model and the person can both look at it now; a hosted link means it can go into a ticket, a document or a message afterwards. Services that return only base64 make the second case a manual upload, and ones that return only a URL make the first case a click. Doing both costs the vendor storage and saves the caller a step. Narrow tool, correct scope: public pages only, no interaction, no waiting for state.
What it is
A single-tool website screenshot service: it renders a public page and returns the image inline plus a hosted URL and page details.
What you get
- take_screenshot captures any public URL, returning the image directly into the conversation as well as a hosted link — so the result is both viewable now and shareable later.
Requirements
SCREENSHOTRENDER_API_KEY. It renders public pages, so anything behind a login is out of scope.
Setup effort
One command plus a key — npx -y screenshotrender-mcp, then supply credentials