"screenshot" matching MCP servers:

A Model Context Protocol server that enables scalable mobile automation for iOS and Android through a platform-agnostic interface, allowing LLMs to interact with mobile applications via accessibility snapshots or screenshot-based inputs.

An MCP server that enables users to control a full Chrome browser running in a Daytona cloud sandbox, allowing web browsing, interaction, and screenshot capture through Claude or other MCP clients.

Enables AI assistants to control an internal Steel Browser via CLI or MCP, allowing URL navigation, session management, and screenshot capture.

An MCP server that lets LLM agents control all Chrome browser tabs via accessibility snapshots, element references, and a virtual cursor, supporting operations like click, type, navigate, screenshot, and video recording.

URL to screenshot, PDF, or structured extract for AI agents via MCP (stdio) and REST. Tools include screenshot, pdf, and extract.

Stripe-native marketplace where AI agents autonomously discover and purchase API services via MCP. Pay-per-call, no accounts needed. 6 live services including Phone Validator, Web Scraper, PDF Generator and Screenshot API.

Provides an MCP server for macOS that allows agents to control a managed browser with accessibility-first actions, visible cursor, and screenshot return.

Enables AI agents to browse, click, type, screenshot, and extract data from web pages without writing CSS selectors, using numbered element refs. It also supports office automation such as bulk form filling, table extraction, downloads, PDF archiving, and page monitoring.

Reliable, scalable browser infrastructure for AI agents. Route, pool, and failover across any browser provider. 8 built-in browser tools using raw Chrome CDP - navigate, screenshot, snapshot, interact, evaluate. Zero-config with auto Chrome detection & concurrent sessions support

Enables AI agents to manage and interact with WebViews in DCC applications through tools like screenshot, load URL, eval JS, and event streaming via the Model Context Protocol.

Headless-browser-as-JSON for AI agents — POST a URL, get rendered HTML, structured DOM, visible text, title, links, and a screenshot from real Chromium, with memorymarket economics where the first agent to render a URL earns 90% of every cache-hit fee from other agents within a 10-minute TTL.

Lets a local Claude Code session drive a visible browser paint editor through four tools — viewing a canvas screenshot, laying down a single brush stroke with real color/size controls, undo/redo, and exporting the finished PNG — so the model can draw an uploaded reference portrait stroke by stroke. Supports optional recording and run-limit settings for comparing drawing quality, timing and CLI cost between a standard and a cost-controlled setup.