Webpage Screenshot MCP Server

@ananddtyagi

代码仓库

基本信息

分类

浏览器自动化

许可证

MIT

传输方式

stdio

作者

ananddtyagi

关于 Webpage Screenshot MCP Server

An MCP that gives your agent the ability to snap a screenshot of webpages. Useful when you want your agent to check its progress during development.

Webpage Screenshot MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "webpage-screenshot": {
      "command": "node",
      "args": [
        "~/path/to/webpage-screenshot-mcp/dist/index.js"
      ]
    }
  }
}

Webpage Screenshot MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Webpage Screenshot MCP Server?

Webpage Screenshot MCP Server is an MCP server that captures screenshots of web pages using Puppeteer. It allows AI agents to visually verify web applications and see their progress when generating web apps.

How to use Webpage Screenshot MCP Server?

Install dependencies with npm install, build with npm run build, then add the server configuration (command node with path to dist/index.js) to Claude Desktop or Cursor settings. Use the provided tools: login-and-wait, screenshot-page, screenshot-element, and clear-auth-cookies.

Key features of Webpage Screenshot MCP Server

Full page or viewport screenshots
Element-specific screenshots via CSS selectors
Supports PNG, JPEG, and WebP formats
Base64 encoded image output
Manual login with cookie persistence
Default browser integration for existing sessions
Session persistence for multi-step workflows

Use cases of Webpage Screenshot MCP Server

Visually verify a web application during development
Take screenshots of protected pages after manual login
Capture specific UI elements for testing or documentation
Automate multi-step workflows that require authentication
Inspect a website’s appearance with your default browser

常见问题

What does this server do?

It provides MCP tools to capture screenshots of web pages (full page, viewport, or specific elements) and return them as base64 encoded images, with support for authentication and session persistence.

How does authentication work?

Use the `login-and-wait` tool to manually log in through a visible browser window; cookies are saved automatically and reused in subsequent `screenshot-page` or `screenshot-element` calls when `useSavedAuth` is true.

What are the runtime requirements?

Node.js is required. The server uses Puppeteer (bundled Chromium) by default, but can also connect to your system’s default browser (Chrome, Edge, or Safari) with `useDefaultBrowser: true`.

What is the difference between headless and visible mode?

Headless mode (`visibleBrowser: false`) is faster for automation; visible mode (`visibleBrowser: true`) shows the browser window, required for `useDefaultBrowser` and manual interactions.

Where are authentication cookies stored?

Cookies are saved to the `.mcp-screenshot-cookies` directory in your home folder. They can be cleared per domain or globally using the `clear-auth-cookies` tool.