localscreenshot

localscreenshot is a screenshot editing tool. A screenshot API aimed at AI agents: ask an assistant for a capture of any web page and get a clean image back via MCP, CLI or REST, with country targeting across 227 locations and options to hide cookie banners, ads and pop-ups.

localscreenshot is a screenshot service built for AI agents rather than for people holding a mouse. The premise is simple: an agent working in ChatGPT, Claude, Cursor, Gemini CLI or a similar client asks for a picture of a web page and receives a clean image back in seconds. There is no browser to install, no headless setup to maintain and no rendering code to write, because the capture happens on the service side and comes back through a connection the agent already understands. Three access routes cover most workflows. An MCP server lets compatible clients call the service directly, a command line tool handles terminal and scripting use, and a REST API serves traditional applications. Captures can be pinned to one of 227 countries, so a page can be seen the way a visitor in Brazil, Japan or Germany would see it, complete with localized content. The service also accepts instructions beyond a plain URL: clicking an element before capturing (opening a menu on a product page, for instance) and hiding cookie banners, ads and pop-ups so the final image shows the page rather than its overlays. Desktop and phone viewports are both supported. The audience is broad for a developer tool. QA teams use it to verify how pages render across regions and devices; marketers and SEO teams audit localized landing pages and competitor layouts; developers embed it in agents and pipelines where a visual check matters. The vendor cites more than 100 users across those groups. Compared with general screenshot APIs, localscreenshot's differentiator is agent-first packaging: the MCP and CLI paths are presented as the primary interface, with documentation written around telling an assistant what to capture in natural language. The main caveat is maturity. The setup page openly marks some client connections as coming later and only publishes instructions it has verified, which means the integration list on the marketing page runs ahead of what actually works today. Anyone evaluating it should confirm their specific client is supported before building around it.