A screenshot tool your agent can call from anywhere.
Point an MCP client at one HTTPS endpoint. Framejet runs the browser, removes common overlays and returns the image inline.
The problem
Shipping a local browser with every agent means maintaining Chromium binaries, sandbox flags, memory limits and platform-specific setup before the agent can inspect one page.
How Framejet handles it
Use the hosted endpoint with an API key. The same account also exposes REST, so an interactive agent and a production job can share billing without sharing implementation code.
Server URL https://framejet.dev/mcp Header Authorization: Bearer YOUR_KEY
Nothing to install
The browser and rendering infrastructure stay on Framejet; the client only speaks MCP over HTTPS.
Clean by default
Cookie banners, consent walls, sticky headers and chat widgets are removed before capture.
Honest quota
Failed captures and cached repeats do not spend a screenshot credit.
Try it on the page your current script cannot reach. No card, 200 screenshots a month, and failures never spend a credit. Get a key.