mcp

This MCP server exposes a tool named render-website-screenshot that allows you to render a webpage and return the resulting image through the MCP framework. Once the server is running, clients can invoke the render-website-screenshot capability to generate screenshots of target URLs, letting you automate visual checks, previews, or testing workflows within your MCP-enabled ecosystem.

To configure usage for Claude or other orchestration environments, supply your ScreenshotOne API key via environment variables or configuration so that the server can authenticate with the ScreenshotOne service. In the Claude desktop config example, the API key is provided under SCREENSHOTONE_API_KEY. When running standalone, set SCREENSHOTONE_API_KEY in the environment before starting the server (for example: SCREENSHOTONE_API_KEY=your_api_key && node build/index.js).

If you’re integrating with other projects, you’ll typically call the MCP endpoint that corresponds to the screenshot tool, supply the target URL and any optional rendering options (such as viewport size or wait time), and receive the screenshot image data in response or as a stream depending on your MCP client implementation.

Prerequisites:

• Node.js (LTS version) installed on your machine
• npm installed (comes with Node)

1. Clone the repository or navigate to the server project directory.
2. Install dependencies and build the project: npm install && npm run build
3. Create or update your MCP environment to include the server under mcp_config, for example configuring the node-based server entrypoint:
   • Ensure the path to build/index.js is correct for your environment
   • Provide your API key via SCREENSHOTONE_API_KEY (or your preferred config method)
4. Start the MCP server using your usual runner or process manager (e.g., node build/index.js or your container runtime).
5. Verify the server is reachable through your MCP client and test the render-website-screenshot capability with a sample URL.

Tips:

• Make sure to supply a valid ScreenshotOne API key; requests without a key will fail authentication.
• If you change the path to the built MCP entry (index.js), update mcp_config accordingly.
• For local development, you can run in verbose mode if supported by your MCP client to help diagnose issues.
• Ensure network access to ScreenshotOne services from the environment where the MCP server runs.
• If you encounter CORS or image rendering issues, check that the target URL is accessible from the server environment and that any required wait times or viewport settings are configured in the rendering options.