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.

Demo

Requirements

• FlowLens browser extension add to chrome and pin for ease of use
• pipx

Getting Started

To install:

pipx install flowlens-mcp-server

To upgrade to the latest version:

pipx upgrade flowlens-mcp-server

To check that the installation was successfully:

flowlens-mcp-server

Add 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-server

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 report

... View full README on GitHub