Screenshot MCP Gateway
A unified MCP server that combines screenshot capture with HTTP/SSE gateway for remote access, enabling full-page and element-specific screenshots via Puppeteer.
README
Screenshot MCP Gateway
A unified MCP (Model Context Protocol) server that combines screenshot capture capabilities with HTTP/SSE gateway functionality for remote access. This project integrates HTTP-ScreenShotMCP with Supergateway to provide a single deployable solution for remote screenshot services.
Features
- ✅ Full-page screenshot capture with Puppeteer
- ✅ Element-specific screenshots using CSS selectors
- ✅ Device viewport presets (mobile, tablet, desktop)
- ✅ Custom viewport configurations
- ✅ Advanced wait conditions (selector, function, timeout, networkidle)
- ✅ HTTP/SSE transport for remote access
- ✅ CORS support for cross-origin requests
- ✅ Headless browser operation (perfect for server deployments)
- ✅ Automatic Chrome installation for headless environments
Quick Start
Installation
npm install
This will automatically:
- Install all dependencies
- Download and configure Chromium for headless operation
- Build the TypeScript source
Running the Server
npm start
The server will start on port 3000 (or the port specified in PORT environment variable).
Endpoints:
- SSE MCP endpoint:
http://localhost:3000/sse - Health check:
http://localhost:3000/health
Configuration
Copy .env.example to .env and customize:
cp .env.example .env
Environment Variables:
PORT: Server port (default: 3000)BROWSER_HEADLESS: Run browser in headless mode (default: true)BROWSER_TIMEOUT: Browser timeout in milliseconds (default: 30000)MAX_CONCURRENT_SCREENSHOTS: Maximum concurrent screenshots (default: 5)
Available MCP Tools
1. capture_screenshot
Capture a full-page screenshot of a webpage with advanced options.
Parameters:
url(required): The URL of the webpage to screenshotviewport(optional): Viewport configurationpreset: Device preset (mobile, tablet, desktop)width: Viewport width in pixelsheight: Viewport height in pixelsdeviceScaleFactor: Device scale factorisMobile: Whether to emulate mobile devicehasTouch: Whether device has touch support
waitFor(optional): Wait condition before taking screenshottype: Type of wait condition (selector, function, timeout, networkidle)value: Value for wait conditiontimeout: Timeout in millisecondsidleTime: Network idle time in milliseconds
standardDelay(optional): Apply standard 2.5s delay after networkidle2 (default: true)delay(optional): Additional delay in millisecondswaitUntil(optional): When to consider navigation complete (default: networkidle2)
2. capture_element
Capture a screenshot of a specific element on a webpage.
Parameters:
url(required): The URL of the webpageselector(required): CSS selector for the element to captureviewport(optional): Viewport configurationstandardDelay(optional): Apply standard 2.5s delay (default: true)
3. list_device_presets
List available device presets with their configurations.
No parameters required.
Usage with MCP Clients
Claude Desktop
Add to your Claude Desktop MCP configuration:
{
"mcpServers": {
"screenshot": {
"command": "npx",
"args": [
"-y",
"supergateway",
"--sse",
"http://localhost:3000/sse"
]
}
}
}
Remote Access
To expose your screenshot server publicly, use ngrok:
# Terminal 1: Start the screenshot server
npm start
# Terminal 2: Expose via ngrok
ngrok http 3000
Then use the ngrok URL in your MCP client configuration:
{
"mcpServers": {
"screenshot": {
"command": "npx",
"args": [
"-y",
"supergateway",
"--sse",
"https://your-ngrok-url.ngrok-free.app/sse"
]
}
}
}
Deployment
Standard Deployment
- Clone this repository
- Install dependencies:
npm install - Build the project:
npm run build - Set environment variables (create
.envfrom.env.example) - Start the server:
npm start
Docker Deployment
Create a Dockerfile:
FROM node:18
# Install dependencies for Puppeteer headless Chrome
RUN apt-get update && apt-get install -y \
chromium \
chromium-sandbox \
fonts-liberation \
libappindicator3-1 \
libasound2 \
libatk-bridge2.0-0 \
libatk1.0-0 \
libcups2 \
libdbus-1-3 \
libgdk-pixbuf2.0-0 \
libnspr4 \
libnss3 \
libx11-xcb1 \
libxcomposite1 \
libxdamage1 \
libxrandr2 \
xdg-utils \
--no-install-recommends \
&& rm -rf /var/lib/apt/lists/*
WORKDIR /app
# Copy package files
COPY package*.json ./
# Install dependencies
RUN npm install
# Copy source code
COPY . .
# Build TypeScript
RUN npm run build
# Set environment variables for headless Chrome
ENV PUPPETEER_SKIP_DOWNLOAD=true
ENV PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium
ENV BROWSER_HEADLESS=true
EXPOSE 3000
CMD ["npm", "start"]
Build and run:
docker build -t screenshot-mcp-gateway .
docker run -p 3000:3000 screenshot-mcp-gateway
Headless Server Requirements
For headless server deployments (Ubuntu/Debian):
# Install Chrome dependencies
sudo apt-get update
sudo apt-get install -y \
chromium-browser \
chromium-codecs-ffmpeg \
fonts-liberation \
libappindicator3-1 \
libasound2 \
libatk-bridge2.0-0 \
libatk1.0-0 \
libcups2 \
libdbus-1-3 \
libgdk-pixbuf2.0-0 \
libnspr4 \
libnss3 \
libx11-xcb1 \
libxcomposite1 \
libxdamage1 \
libxrandr2 \
xdg-utils
Development
Build
npm run build
Development Mode (with auto-reload)
npm run dev
Clean Build Artifacts
npm run clean
Architecture
This project combines:
- Screenshot MCP Server: Provides screenshot capture functionality using Puppeteer
- Supergateway Pattern: HTTP/SSE transport layer for remote MCP access
- Express.js: Web server framework
- MCP SDK: Official Model Context Protocol SDK
- Puppeteer: Headless Chrome automation
Security Considerations
- The server is exposed on the network when running in HTTP mode
- Consider implementing authentication for production deployments
- Use environment variables for sensitive configuration
- Implement rate limiting for production use
- Be cautious with URL inputs to prevent SSRF attacks
Troubleshooting
Chrome Installation Issues
If Chrome fails to install automatically:
npx puppeteer browsers install chrome
Headless Mode Issues
If screenshots fail in headless mode, try:
- Set
BROWSER_HEADLESS=falsefor debugging - Check Chrome dependencies are installed
- Verify Chrome executable path
Connection Issues
- Ensure the port is not already in use
- Check firewall settings for the specified port
- Verify CORS settings if accessing from web clients
License
MIT
Credits
This project integrates:
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.