ScreenshotOne

You deploy a dedicated MCP server that connects AI assistants to the ScreenshotOne.com API to capture and render website screenshots. This enables you to take URL screenshots, render HTML, customize viewports, block ads, and output in multiple formats, all through a standardized MCP interface.

How to use

You run an MCP client against the server to perform screenshot tasks. The server exposes both a remote HTTP endpoint and a local stdio server for integration with your tooling. Use the HTTP transport when calling from web-based clients, and use the stdio transport for command-line and local automation. Typical usage patterns include taking a screenshot of a URL, rendering HTML, capturing full-page screenshots, applying device emulation, blocking ads and trackers, injecting custom CSS/JS, and saving outputs in PNG, JPEG, WebP, or PDF.

How to install

# Prerequisites
- Node.js (>=18.x)
- npm (comes with Node.js)

# 1) Install dependencies and run from source (example)
# The MCP server can run as a local stdio service or as an HTTP endpoint. The following demonstrates starting a local stdio server and the HTTP variant.

# Local stdio server
npm install
# Then start the server (stdio)
npm run dev:server

# Remote HTTP transport
npm run dev:server:http

Configuration and deployment notes

Configure how your MCP server runs by choosing either a local stdio setup or a remote HTTP setup. The stdio configuration starts the server locally with a node command and points to the built entry file. The HTTP configuration exposes the MCP endpoint over HTTP. Environment variables control host, port, and endpoint path for the HTTP transport.

Environment and runtime configuration

HTTP Transport environment variables you can set to customize the HTTP server:

• MCP_HTTP_HOST: The host to bind to (default: 127.0.0.1)
• MCP_HTTP_PORT: The port to listen on (default: 8080)
• MCP_HTTP_PATH: The endpoint path (default: /mcp)

Running with examples

Below are example commands you can adapt to your environment. These demonstrate starting the server in development with the stdio transport and starting the HTTP transport variant. Replace paths and keys with your actual values.

# Start local stdio MCP server (example snippet)
npm run dev:server

# Start HTTP MCP server (example snippet)
npm run dev:server:http

Testing the screenshot tool via MCP

After the server is running, you can test taking screenshots through an MCP client. Use the client to request a screenshot of a URL, specify viewport sizes, enable full-page captures, or apply block rules like ads or trackers. You can also request different output formats and filenames as part of your integration.

Notes on debugging and inspector

For debugging during development, enable verbose logs and use the built-in MCP Inspector to test requests and responses. The inspector provides a visual interface to verify tool calls, data flow, and formatting.

Publishing and maintenance

When you are ready to publish your own MCP server configuration, ensure you have a production-ready build and validated tests. Use your preferred publishing workflow and ensure environment variables and endpoints are correctly documented for your users.

Available tools

ip_lookup

IP lookup tool to fetch geolocation/ownership details for an IP address using the MCP server tooling.

get_data

Tool to fetch data from an example API and present it as Markdown-formatted content.