Let Your AI Agent Drive a Real Chrome Window
The Seller Labs Playwright MCP gives Claude Code or Codex a visible Chrome browser it can click, type and read in. You log in once, then watch it work through Seller Central pages and other websites, and take over whenever you want.
View on GitHub → MIT licensed. Runs on your own computer, and nothing in it connects to Seller Labs.A Browser Built for Real Seller Work
Most browser tools for AI agents open a blank, throwaway browser. This one uses your own Chrome and keeps it open.
Your real Chrome
It runs the Google Chrome you already have, so your extensions work, including your password manager. Your password manager fills in your logins, so you keep control of your passwords instead of handing them to your AI.
Log in once
The browser profile persists. Sign in to Seller Central yourself, and every later agent session starts already logged in.
Survives closing the chat
When an agent session ends, only its own tabs close. Chrome and your logins stay up for the next session.
Watch or take over
The window is visible on your screen. You can see every click and step in at any point, for example to approve a two-step login.
Downloads land where you expect
Reports and files the agent downloads go to your normal Downloads folder, with the right file extension.
Leaner pages for the AI
Large pages are trimmed before your agent reads them, which saves context on busy screens like search results.
Install It With One Prompt
This installs the Playwright MCP on its own. You do not need the rest of the AI Toolbox.
-
1
Install the basics
Node.js 18 or newer, git, Google Chrome, and an AI coding agent: Claude Code or Codex.
-
2
Paste this prompt into Claude Code or Codex
Clone https://github.com/sellerlabs/slt-toolbox-public and set up ONLY the Playwright MCP, following mcps/playwright-mcp/README.md. In that folder run npm install and npx playwright install. Then register playwright-mcp-visible.js with yourself as an MCP server named playwright-visible, using the file’s absolute path. Skip Lazy Hub and every other tool in the repo. Tell me when it is done. -
3
Restart your agent and try it
Start a new session so the browser tools load, then ask something like “Open sellercentral.amazon.com in the visible browser.” Chrome opens on the first request. In Codex, approve the browser tool when it asks.
Works on Both
Mac
The shared browser server starts in the background the first time your agent uses a browser tool. Nothing else to configure.
Windows
On first use it registers a Scheduled Task named PlaywrightMcpSharedServer, so Chrome stays open after your editor closes. The task runs as you, with no admin rights or UAC prompt.
Ground Rules That Keep It Safe
You log in, not the agent. Sign in to Seller Central and other accounts yourself in the visible window. Never paste a password into the chat.
Start with read-only tasks. Have it look things up, pull reports and summarize pages before you let it change a listing, a price or a setting.
Review before anything is saved. Ask the agent to stop at the confirmation screen so you can check it, then give the go-ahead yourself.
The browser stays on your machine. It runs locally, and credential-shaped values are masked before page content reaches the AI.
Pair It With the Seller Labs MCP Server
The browser is best for pages and actions that have no data feed. For numbers, a direct data connection is faster and more reliable than reading screens.
The Seller Labs MCP Server connects Claude to your Seller Central data, including orders, inventory, advertising and profit. Use both: the data connection for analysis, the browser for everything else.
Go Further
- AI Toolbox: the full free toolbox, with a task scheduler, Google Workspace, Slack and more.
- Playwright MCP lesson: a course module on browser automation for Amazon sellers.
- Amazon Courses: Seller Labs courses for Amazon sellers, including AI automation.
Get the Playwright MCP
Free, open source and yours to customize. Star the repo to follow updates.
View on GitHub →