Viewport And Device Emulation

via “viewport and browser configuration injection at session creation”

Run cloud browser sessions and web automation via Browserbase MCP.

Unique: Applies viewport and browser configuration at the cloud browser infrastructure level (Browserbase) rather than through client-side APIs, ensuring consistent rendering across all interactions and eliminating viewport mismatch issues between screenshot capture and interaction execution

vs others: More reliable than Puppeteer/Playwright viewport configuration because it's enforced at the cloud browser level; enables testing multiple viewports in parallel without resource contention on local machines

via “emulation and device simulation”

Chrome DevTools for coding agents

Unique: Configures device emulation at server startup via CLI arguments (--deviceType or custom viewport), enabling persistent device simulation across all requests without per-request configuration overhead.

vs others: Provides persistent device emulation configuration (vs Puppeteer's per-page setViewport), reducing setup overhead for agents testing consistent device profiles, though at the cost of requiring separate server instances for multi-device testing.

via “emulation-and-device-simulation”

Chrome DevTools for coding agents

Unique: Uses Chrome DevTools Protocol Emulation domain to apply device profiles, network throttling, and geolocation spoofing at the browser level, enabling consistent simulation across test runs. Supports both predefined device profiles and custom configurations, providing flexibility for different testing scenarios.

vs others: Applies emulation via CDP (vs visual viewport resizing), providing accurate device simulation including user agent and network throttling, whereas simple viewport resizing does not simulate network conditions or device-specific behavior.

via “viewport-and-device-emulation”

MCP server for Chrome DevTools

Unique: Exposes CDP's Emulation domain through MCP, allowing agents to dynamically change viewport and device settings without restarting the browser. Supports device presets for common devices, reducing configuration overhead.

vs others: More flexible than Puppeteer's setViewport() because it also supports device emulation (user agent, touch, device pixel ratio) in a single call, and allows agents to switch between device profiles without page reload.

via “viewport and device emulation configuration”

** - An MCP server using Playwright for browser automation and webscrapping

Unique: Exposes Playwright's device emulation and viewport configuration as MCP tools, supporting both preset device profiles and custom viewport dimensions. Enables mobile-specific testing without physical devices.

vs others: More comprehensive than simple viewport resizing; includes device-specific user agents, touch event support, and preset profiles for common devices, enabling realistic mobile testing.

via “mobile and responsive design testing with viewport configuration”

Claude Code Skill for browser automation with Playwright. Model-invoked - Claude autonomously writes and executes custom automation for testing and validation.

Unique: Integrates Playwright's device emulation and viewport configuration into the skill's patterns, allowing Claude to generate code that tests multiple viewport sizes and mobile devices in a single automation flow. This is documented as an advanced topic in SKILL.md.

vs others: Provides device emulation through Playwright's native capabilities, enabling multi-device testing without external services, whereas manual device testing requires physical devices and cloud device labs require external services and costs.

via “viewport-and-device-emulation-configuration”

Fork and update (v0.6.5) of the original @modelcontextprotocol/server-puppeteer MCP server for browser automation using Puppeteer.

Unique: Exposes Puppeteer's device emulation as MCP tools, allowing agents to dynamically switch device profiles and viewport sizes without managing Puppeteer's emulate() API or device descriptor objects directly.

vs others: Simpler than raw Puppeteer device emulation because it abstracts device profiles and provides them as named options, vs. requiring agents to construct device descriptor objects manually.

via “viewport and device emulation configuration”

** - A MCP server that provides comprehensive website snapshot capabilities using Playwright. This server enables LLMs to capture and analyze web pages through structured accessibility snapshots, network monitoring, and console message collection.

Unique: Leverages Playwright's built-in device emulation profiles to enable multi-device testing without managing separate browser instances, allowing LLMs to analyze responsive layouts

vs others: More efficient than launching multiple browsers because it reuses browser context with different device profiles; more comprehensive than viewport-only changes because it includes user agent and device pixel ratio

via “viewport-and-device-emulation”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Provides device emulation as an MCP tool, allowing agents to test responsive behavior without manual viewport configuration. Includes preset device profiles for common devices.

vs others: More convenient than manual viewport configuration because it includes device presets; more realistic than simple viewport resizing because it includes device metrics and user agent.

via “parameterized website rendering with viewport and device emulation”

** - Render website screenshots with [ScreenshotOne](https://screenshotone.com/)

Unique: Exposes ScreenshotOne's full parameter set (viewport, device type, wait conditions) through MCP's typed tool schema, allowing agents to declaratively specify rendering context without string concatenation or manual API payload construction. Parameters are validated against ScreenshotOne's constraints before transmission.

vs others: More flexible than headless browser libraries (Puppeteer, Playwright) for cloud-based rendering; avoids managing browser lifecycle and resource overhead while supporting device emulation natively through ScreenshotOne's infrastructure

via “viewport and rendering options configuration”

MCP server: url-to-image-mcp

Unique: Exposes rendering parameters as MCP tool inputs, allowing agents to request specific viewport/format combinations without server-side configuration changes. Likely uses Puppeteer/Playwright's viewport and emulation APIs directly, passing agent-specified options through to the browser.

vs others: More flexible than fixed-viewport rendering; agents can adapt rendering to content type. More discoverable than environment variables or config files because parameters are part of the MCP tool schema.

via “mobile device emulation with device profiles”

A high-level API to automate web browsers

Unique: Provides predefined device profiles for popular mobile devices (iPhone, Android) with automatic viewport, user agent, and device pixel ratio configuration, enabling mobile testing without physical devices or external emulation tools

vs others: More convenient than manual viewport configuration because device profiles are pre-configured, and more integrated than external device emulation because it operates within the browser context