Website Screenshot MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Website Screenshot MCPcapture a screenshot of github.com as it appears on an iPhone and save it to my desktop"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Glasses MCP: Let Your AI See the Web 👓
Your AI assistant is a powerful partner, capable of processing immense amounts of text and code. But when it comes to the visual web, it's flying blind. It can't see the layout of a competitor's landing page, the design of a complex dashboard, or the look of your latest prototype.
Glasses MCP gives it sight.
It's a simple tool that allows your AI to request a perfect, device-specific screenshot of any website. It's not just about taking pictures; it's about giving your AI the context it's been missing, turning the visual web into a resource it can finally understand and interact with.
Table of Contents
Related MCP server: BrowserLoop
Features
Capture any URL: Take a screenshot of any public website or local development server.
Device Emulation: See how a site looks on a variety of popular phones, tablets, and laptops.
Selectable Format: Choose between
pngandjpegimage formats.Full Page or Viewport: Capture the entire scrollable page or just the visible viewport.
Structured Output: Returns a clear JSON object indicating success or failure.
Installation
You can install Glasses MCP in two ways, depending on your preference and client application.
Method 1: Desktop Extension
This is the easiest way to get started. It allows for one-click installation in compatible clients like Claude Code.
Open the
.dxtfile with your client application. The client will handle the rest.
Method 2: Manual JSON Configuration
This method uses npx to download and run the package on-demand. It's ideal for command-line usage or for developers who prefer not to install the extension directly.
To use this method, add the following JSON to your client's configuration file:
{
"mcpServers": {
"glasses": {
"command": "npx",
"args": ["-y", "glasses-mcp"]
}
}
}Configuration File Locations:
For Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.jsonFor Gemini CLI:
~/.gemini/settings.jsonFor Cursor IDE: Your user
settings.jsonfile.
Usage
Once integrated, you can use prompts like these with your AI assistant.
Example Prompts
Here are a few examples of how you can use Glasses MCP.
For a straightforward capture of a homepage, where the AI can infer the filename:
"Take a screenshot of github.com and save it to my desktop."
To specify a different image format and save location:
"Get a JPEG screenshot of the latest news on bbc.com/news and save it in my downloads folder."
To see how a website looks on a mobile device, specifying the exact output filename:
"Capture the verge.com homepage as it would appear on a small iOS device and save it as
verge-mobile.png."
To capture a local development server, focusing only on the visible portion of the page:
"Capture just the viewport of my local server at
http://localhost:3000."
Tool Reference: screenshot
Name | Type | Required | Default | Description |
|
| Yes | - | The full URL of the website to capture. |
|
| Yes | - | The local file path to save the screenshot to. |
|
| No |
| The output image format. |
|
| No |
| If |
|
| No |
| The name of the device to emulate (see Supported Devices below). |
Supported Devices
The screenshot tool can optionally emulate a specific device, which sets the viewport size, pixel density, and user agent to match. We have curated a list of popular and representative devices to provide good coverage of the most common form factors while keeping the list manageable.
Device Name | Device ID | Category | Represents |
|
| Phone | A large, modern iOS device. |
|
| Phone | A smaller, older-generation iOS device. |
|
| Phone | A large, modern Android device. |
|
| Phone | A common, slightly older Android device. |
|
| Tablet | A modern, high-resolution tablet. |
|
| Tablet | A smaller, popular tablet format. |
|
| Laptop | A high-resolution laptop (e.g., MacBook Pro). |
|
| Laptop | A standard-resolution laptop. |
Returns: A JSON object indicating success or failure.
{
"success": true,
"outputPath": "/path/to/your/screenshot.png"
}Error Handling
If the tool encounters an error (e.g., an invalid URL, a website that fails to load), it will return a JSON object with the isError flag set to true and a descriptive error message.
{
"success": false,
"error": "net::ERR_NAME_NOT_RESOLVED at https://invalid-url-here.com"
}Limitations
No Login/Authentication: The tool cannot log in to websites that require authentication. It can only capture publicly accessible content.
Anti-Bot Measures: Some websites employ sophisticated anti-bot technologies that may block the tool from capturing a screenshot.
Complex Interactions: The tool does not support complex interactions like clicking buttons, filling out forms, or scrolling to a specific element before taking a screenshot.
Development & Contributing
To contribute to this project:
Clone the repository:
git clone https://github.com/gourraguis/glasses-mcp.gitInstall dependencies:
cd glasses-mcp && npm installBuild the project:
npm run buildTo test your local build, use the MCP Inspector:
npx @modelcontextprotocol/inspector node dist/main.js
Available Tools
1 toolscreenshotWebsite ScreenshotC
Takes a screenshot of a website.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| outputPath | Yes | ||
| format | No | ||
| fullPage | No | ||
| device | No | laptop-hidpi |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral details such as whether the screenshot is saved locally or returned as data, browser rendering nuances, or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (one sentence) but fails to front-load essential information or justify its brevity given the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description does not cover return values, side effects, or required permissions, making it insufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description provides no explanation for any of the 5 parameters, leaving the agent to infer meaning from schema names alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Takes a screenshot of a website' clearly states the primary action and resource, but lacks specificity about features like full-page or device emulation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool, no context on alternatives (none provided), and no indication of prerequisites or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of confusion or overlap between tools.
A single tool has no pattern to break, so naming is trivially consistent.
One tool for a specific screenshot purpose is borderline; it feels thin but could be acceptable for a minimal server.
The server lacks common parameters (e.g., viewport size, full-page option, delay) that agents would typically need, leaving significant gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Screenshot any website with one API call PNG, JPEG, WebP, or PDF. Custom viewports, device emulation, ad blocking, dark mode, and smart caching.
Generate images, GIFs, and PDFs from HTML, URLs, or templates — from your AI agent.
Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API
Desktop and mobile website screenshots plus page context for AI agents and automation workflows.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to capture and analyze web page screenshots using Puppeteer, supporting multi-breakpoint captures, error reporting, and page interactions.1486MIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server for taking screenshots of web pages using Playwright, allowing AI agents to automatically capture and analyze screenshots for UI verification or other tasks.91423AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceA server that enables AI assistants to control a browser through tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
- AlicenseNot gradedqualityCmaintenanceEnterprise-grade screenshot capture server for AI agents with multi-format support, PII masking, multi-monitor support, and security controls for capturing full screens, specific windows, or custom regions across Linux, macOS, and Windows.942MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gourraguis/glasses-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server