ScreenshotOne MCP Server

What is ScreenshotOne MCP Server about?

A lightweight MCP server that exposes the render-website-screenshot tool, allowing clients (e.g., Claude for Desktop) to request website screenshots and receive them as image binaries.

How to use ScreenshotOne MCP Server?

Install dependencies and build
```
npm install && npm run build
```

Set your ScreenshotOne API key

export SCREENSHOTONE_API_KEY=your_api_key   # Unix/macOS
set SCREENSHOTONE_API_KEY=your_api_key      # Windows CMD

Run the server
```
node build/index.js
```

Configure a client (e.g., Claude for Desktop) by adding the following to claude_desktop_config.json:

{
  "mcpServers": {
    "screenshotone": {
      "command": "node",
      "args": ["path/to/screenshotone/mcp/build/index.js"],
      "env": { "SCREENSHOTONE_API_KEY": "<your api key>" }
    }
  }
}

Key features of ScreenshotOne MCP Server

Implements the MCP render-website-screenshot tool.
Simple build‑and‑run workflow with npm.
Secure API key handling via environment variable.
Compatible with Claude for Desktop and any MCP‑compatible client.

Use cases of ScreenshotOne MCP Server

AI agents that need visual context from web pages.
Automated testing pipelines that capture page renders.
Integrations where a remote service must supply screenshots on demand.
Personal productivity scripts that fetch site thumbnails.

FAQ from the ScreenshotOne MCP Server

Do I need to build the project before running it? Yes. Run npm install && npm run build to compile the TypeScript source.
Where do I obtain the API key? Sign up at https://screenshotone.com and generate an API key in your account dashboard.
Can I run the server without building? The source is TypeScript; building is required unless the package is published with pre‑built JavaScript.
Is the server compatible with other MCP clients? Absolutely – any client that follows the MCP specification can invoke the render-website-screenshot tool.
What environment variable is used for the key? SCREENSHOTONE_API_KEY.