Periscope MCP

What segentic-lab/periscope-mcp MCP server does

segentic-lab/periscope-mcp MCP server is designed for agent-driven QA of static sites, single-page applications, and authenticated web apps. It exposes Playwright-backed operations through MCP, but organizes them around testing tasks rather than only low-level browser bindings. Agents can create projects, configure authentication, discover pages, run checks, interact with controls, and retrieve saved evidence.

Testing can cover a single URL or an entire project. Results may include structured verdicts, screenshots, captured response bodies, console and network information, reports, and session dossiers. The documented checks include accessibility, SEO, visual and functional issues, responsive behavior, GEO readiness, Lighthouse results, and interaction-based INP measurement.

How it works

An MCP client starts the server over stdio. The server dispatches tool calls to Playwright and headless Chromium, while maintaining project data, browser sessions, screenshots, videos, and reports. Crawling uses same-domain page discovery, and persistent sessions allow later actions to reuse an authenticated browser context.

Authentication can be configured with a form login, HTTP Basic Auth, or injected cookies. For 2FA, SSO, or CAPTCHA, an agent can open a visible browser window, complete the login manually, and save the resulting session for later headless runs. Sessions can also be opened, closed, listed, resized, and switched to a popup or new tab.

The interaction model supports individual actions and grouped workflows. Agents can click elements, fill forms, select native or custom dropdowns, scroll to elements, inspect matching page elements, and run multi-step sequences. Named flows can be saved, executed, listed, or deleted for reuse.

Setup and configuration

The documented prerequisites are Python 3.11 or newer and Playwright with Chromium. The repository provides an installation script that can install dependencies, create a virtual environment, install the Playwright browser, run a headless self-test, and generate an MCP configuration file with absolute paths.

On Debian or Ubuntu, the quick installation path may install system prerequisites. Options are available to use an existing Chromium or Chrome binary through CHROMIUM_PATH, skip dependency installation, or run without interactive confirmation. Other operating systems receive platform-specific manual commands from the installer. An update script refreshes source, dependencies, browser components, and generated configuration without removing the runtime data directory.

Tools and capabilities

The listed tool groups support:

• Project creation, lookup, listing, and deletion.
• Form, Basic Auth, cookie, interactive, and copied authentication state.
• Single-page tests, same-domain crawling, full project audits, screenshots, and saved reports.
• Persistent browser sessions, viewport presets or custom dimensions, popup adoption, and session cleanup.
• Element inspection, clicks, form filling, dropdown selection, scrolling, and reusable flows.
• Network interception, captured diagnostics, screenshots, videos, state information, and structured test results.

Limitations and notes

segentic-lab/periscope-mcp MCP server runs through stdio and requires a local Python and Chromium environment. Authentication data, project files, screenshots, reports, and other runtime artifacts are stored in the repository's data directory, so that directory contains sensitive information when credentials or authenticated sessions are used.

The crawler is described as same-domain only. Interactive login requires a visible browser window, while saved sessions can subsequently run headlessly. The material distinguishes this project from general browser-control servers: it is intended for testing and reporting, not merely browsing or extracting page content. The repository says it works with any MCP client that supports its stdio connection.