FlowLens MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FlowLens MCP Serveranalyze the console errors from my last recording"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FlowLens MCP
flowlens-mcp-server gives your coding agent (Claude Code, Cursor, Copilot, Codex) full browser context for in-depth debugging and regression testing.
How it works
Record your browser flow using the FlowLens Chrome extension (user actions, network, console, storage, DOM events/screen recording).
Share it with your coding agent via the FlowLens MCP server, giving the agent full access to the recording.
Your agent inspects and analyzes the flow for debugging and insights — without spending time/tokens on reproducing the issue.
Related MCP server: Krometrail
Demo
Requirements
FlowLens browser extension add to chrome and pin for ease of use
Getting Started
To install:
pipx install flowlens-mcp-serverTo upgrade to the latest version:
pipx upgrade flowlens-mcp-serverTo check that the installation was successfully:
flowlens-mcp-serverAdd FlowLens MCP server
Add the following config to your MCP client (ex: ~/.claude.json) under mcpServers:
"flowlens": {
"command": "flowlens-mcp-server",
"type": "stdio"
}MCP Client configuration
claude mcp add flowlens --transport stdio -- flowlens-mcp-serverClick the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.
code --add-mcp '{"name":"flowlens","command":"flowlens-mcp-server"}'codex mcp add flowlens -- flowlens-mcp-server"flowlens": {
"command": "flowlens-mcp-server"
}Note:
The above setup only works with local flows. If you want to also connect to shareable flows, get your FLOWLENS_MCP_TOKEN from the FlowLens platform and add it to your relevant MCP config file:
"flowlens": {
"command": "flowlens-mcp-server",
"type": "stdio",
"env": {
"FLOWLENS_MCP_TOKEN": "YOUR_FLOWLENS_MCP_TOKEN"
}
}Usecases:
Bug reporting
Use FlowLens to quickly report bugs with full context to your coding agent. You no longer need to copy-paste console logs, take multiple screenshots, or have the agent spend tokens on reproducing the issue.
Regression testing
Use FlowLens to record your crticial user flows and ask your coding agent to auto test these flows or generate corresponding playwright test scripts
Shareable flows
Share captured flows with your teammates on the FlowLens platform and debug with your coding agent by adding a generated access token in the MCP config. More on this here
This server cannot be deployed
Maintenance
Related MCP Connectors
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
- TabfleetOAuthcom.tabfleet
Launch, inspect, control, and share isolated cloud browsers for your agents.
AI agent run monitoring with incident replay and SLA receipts.
Gives your coding agent the captured console, network, replay and screenshot evidence for a bug.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceRecords, replays, and correlates visual and API events in the browser, enabling AI assistants to understand which API calls feed which UI elements.MIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents eyes into running applications by recording browser activity and providing session investigation tools for debugging.9 npm3MIT
- AlicenseAqualityBmaintenanceRecords every browser session (screen, DOM, network, console, storage) and enables time-travel debugging to rewind and analyze failures.623 npmMIT
- AlicenseNot gradedqualityBmaintenanceRecords browser sessions and provides structured context (clicks, console, network, screenshots) for AI coding agents to understand and act upon.2MIT