Periscope MCP server

periscope-mcp

An MCP server that gives AI agents 74 Playwright tools to QA, test, and analyze web apps — static sites, SPAs, and apps behind a login — returning hard verdicts, not screenshots to squint at. Not a thin wrapper around browser APIs; the tools are shaped around how agents actually work:

passed: true/false with the actual value; checks return structured issues.

• Hard results, not screenshot-squinting — assert_condition returns

whole form; interactandtest batches 25 action types with checks; test_project crawls and audits an entire site.

• One call instead of ten — autofillform detects, infers, and fills a

cookie auth, plus a visible interactive login for 2FA/SSO/CAPTCHA that then runs headless), multi-step flows, network mocking, state snapshots, and real INP measured from the interactions it drives.

• Real web-app testing — persistent authenticated sessions (form/basic/

(expired session vs. browser crash vs. eviction); silent no-ops like ignored drags come back flagged, not as fake success.

• Honest responses — failures say what happened and what to do next

network mocking, and state snapshots/diffs, no setup calls needed.

• Debugging built in — captured API response bodies, console/network logs,

GEO/agentic-search readiness (robots.txt AI-crawler access, llms.txt, WebMCP), plus real Lighthouse.

• Audits agents can't get from a browser binding — accessibility, SEO, and

Playwright + headless Chrome underneath; site crawling, responsive testing, and screenshot diffing on top. Works with any MCP client — Claude Code, Codex, Cursor, Windsurf, Gemini CLI, custom agents, or anything else that speaks MCP over stdio.

Why not just playwright-mcp?

playwright-mcp is excellent at what it is: general browser control over MCP, with tools that mirror Playwright's own API. If the job is "browse this site, click around, extract something," use it.

Periscope exists for a different job: testing and auditing a site or web app, then reporting findings — and its tools encode the testing knowledge an agent would otherwise have to reinvent every session:

The two aren't rivals — an agent can happily use playwright-mcp for browsing tasks and Periscope when it's wearing the QA hat. Periscope's design bets are simply about that hat: fewer, higher-level calls; structured verdicts instead of raw page state; and errors written to tell the agent what to do next.

Architecture

Shortened. The full README is on GitHub.