# screenshot

**Category:** 📂 Browser Automation  
**Repository:** https://apiscreenshot.com  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/screenshot

## Description
Screenshot any URL/HTML as PNG/JPEG/WebP, or read it as clean Markdown/text for LLMs.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What screenshot MCP server does

The screenshot MCP server provides two related ways to process web content. Given a URL or HTML, it can produce an image in PNG, JPEG, or WebP format. It can also read the same kind of input and return clean Markdown or plain text for use by language models.

This makes the service relevant to agents that need to inspect a page visually, save a rendered representation, or work with page content without handling raw HTML directly. The available description does not identify separate product areas or additional data sources beyond URLs and HTML.

## How it works

An agent supplies either a web URL or HTML as the source input. For visual output, the screenshot MCP server returns a capture in one of the listed image formats: PNG, JPEG, or WebP. For text-oriented workflows, it returns cleaned Markdown or text instead of an image.

The two output paths support different agent tasks. Image output can be passed to a workflow that needs a rendered page representation. Markdown or text output is suited to workflows that need page content in a form an LLM can process.

## Tools and capabilities

The documented capabilities are:

- Capture a URL as PNG.
- Capture a URL as JPEG.
- Capture a URL as WebP.
- Capture HTML as PNG, JPEG, or WebP.
- Read URL or HTML content as clean Markdown.
- Read URL or HTML content as plain text for LLM use.

The description does not provide formal tool names, argument schemas, return schemas, limits, or examples. Treat the formats and input types above as the supported surface documented for this listing rather than assuming additional browser or content-processing controls.

## Limitations and notes

The screenshot MCP server listing does not include a README, installation instructions, configuration details, environment variables, transport information, authentication guidance, or client compatibility notes.

It also does not document behavior for dynamic pages, protected URLs, redirects, embedded resources, large documents, or conversion errors. Those details should be confirmed from the service documentation before relying on the screenshot MCP server for production workflows. The supported output formats and Markdown/text conversion are the only documented capabilities available here.

_Full upstream README: https://allmcps.com/mcp/screenshot/readme_