LabscoMCP early access ↗
Abhi5h3kMCP SERVER

MCP URL2SNAP

Screenshot any URL from a conversation and get back a link to the captured image.

by Abhi5h3k ↗Browser Automation, Control & ScreenshotsCommunity

LABSCO SUMMARY

One job, and the return shape is the good decision.

Handing back a URL instead of image bytes keeps the response cheap and makes the capture something you can paste into a ticket or a document. Because the rendering happens at AbstractAPI rather than locally, there is no browser to install and no headless Chrome to keep alive — the trade is that every capture goes through a third party on your key.

What it is

A lightweight MCP server that captures a screenshot of a given URL through AbstractAPI's screenshot service and returns only the access URL for the image — so the result is a link to share or embed rather than a payload to carry around.

What you get

  • A screenshot of any URL you name, taken on request
  • Just the access URL in return, which keeps the response small and makes the image shareable
  • A plain-language trigger — asking to show the screenshot of a page is enough

Requirements

An AbstractAPI key for their screenshot API, put in a .env file as ABSTRACT_API_KEY or in the client config's env block. Python 3.11.0 or higher and UV 0.6.9 or higher. Installation is a clone plus uv venv and uv install, then uv run server.py; the client config runs uv with --directory pointing at the checkout. The project is snap-sense (version 0.1.0).

Setup effort

Build from source