ScreenshotOne.com - MCP Server logo

ScreenshotOne.com - MCP Server

by mrgoonie

This project provides a Model Context Protocol (MCP) server that connects AI assistants to ScreenshotOne.com API to capture screenshots of websites. It enables AI systems to securely and contextually capture website screenshots.

View on GitHub

Last updated: N/A

What is ScreenshotOne.com - MCP Server?

This is a Model Context Protocol (MCP) server that allows AI systems to connect with the ScreenshotOne.com API to capture website screenshots. It implements the MCP specification with a clean architecture, enabling AI assistants to capture screenshots of websites programmatically.

How to use ScreenshotOne.com - MCP Server?

The server can be used via CLI or HTTP transport. The CLI allows taking screenshots with various options like URL, viewport size, and output format. The HTTP transport allows web-based clients to interact with the server. Configuration details and examples are provided in the README.

Key features of ScreenshotOne.com - MCP Server

  • Take screenshots of any URL

  • Render HTML content and take screenshots

  • Customize viewport size and device emulation

  • Capture full-page screenshots

  • Select specific elements using CSS selectors

  • Multiple output formats (PNG, JPEG, WebP, PDF)

  • Block ads, trackers, and cookie banners

  • Inject custom CSS and JavaScript

  • Control wait behavior and timing

Use cases of ScreenshotOne.com - MCP Server

  • Automated screenshot generation for AI assistants

  • Website monitoring and archiving

  • Visual testing and quality assurance

  • Content creation and sharing

  • Programmatic website analysis and reporting

FAQ from ScreenshotOne.com - MCP Server

What is MCP?

Model Context Protocol (MCP) is an open standard that allows AI systems to securely and contextually connect with external tools and data sources.

What transports are supported?

The server supports stdio and Streamable HTTP transports.

How do I configure the HTTP transport?

You can configure the HTTP server using environment variables like MCP_HTTP_HOST, MCP_HTTP_PORT, and MCP_HTTP_PATH.

How do I run the server in development mode?

Use the command npm run dev:server for stdio transport or npm run dev:server:http for HTTP transport.

How do I add my own tools to the server?

Follow the steps in the 'Building Custom Tools' section of the README, which includes defining a service layer, creating a controller, implementing an MCP tool, and adding CLI support.