flow
Save / run / list / delete named step sequences (reusable workflows)
How to use it
flow is exposed by the Periscope MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the flow tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Periscope MCP
pip install -r requirements.txtOther tools in Periscope MCP (39)
Comprehensive link checker (internal + external)
Click element (force=true bypasses overlays)
Close session and free resources
Pixel diff between two screenshots
Copy auth config + session state between projects
Discover all pages from base URL
Create a new testing project
Delete project + data
Fill form fields, optionally submit
Export real INP time series (per interaction) as JSON/CSV + percentile stats
List matching elements with attributes
Get project details
Read a report file
Get screenshot file path
Parse HTML table into structured JSON (headers → cell values)
Capture visible toast/notification messages
Multi-step workflow with 25 actions (see below)
Open a visible window to log in by hand (2FA/SSO/CAPTCHA), then savelogin
List all projects
List saved test reports
List all active sessions
Execute login using configured auth
Measure click-to-result timing
Open persistent browser session (headed=true for a visible window)
Real Google Lighthouse audit: 0-100 scores, Core Web Vitals, failed audits (needs Node.js)
Capture the manual-login session; the project then runs authenticated + headless
Scroll element into viewport without clicking
Native <select> or custom dropdown (Radix/shadcn) — auto-detects
Adopt a popup/new tab (OAuth, target=blank) as a new drivable session
HTML+PDF dossier of every tool call this run — args (redacted), verdicts, timings, screenshots
Configure HTTP Basic Auth
Inject session cookies
Configure username/password form login
Switch viewport size (8 device presets or custom w/h)
Analyze form validation messages
Full audit: crawl + test all pages
Test at mobile/tablet/desktop viewports
Test a single URL (screenshot + checks)
Named visual-regression baselines: set once, check for a hard pass/fail