Browser Use
by browser-use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Computer or cloud★ 120,087MITUpdated 16 days ago
Install
PlaywrightGen
Overview
Description from the maker (original English)
Approved test intent, reviewed Playwright automation and run evidence, inside your editor.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Web & browsers
- You need to fill in: Authorization
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- You fill in yourself:
Authorization
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http playwrightgen https://playwrightgen.com/api/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"playwrightgen": {
"url": "https://playwrightgen.com/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"playwrightgen": {
"type": "http",
"url": "https://playwrightgen.com/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
Authorizationsecret required HTTP headerBearer , where the token is the personal editor token from your project's Automation page in PlaywrightGen. It speaks for you, proposes but never approves, and stops working when your access ends.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain playwrightgen.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Web & browsersi
- More stars than 0% of the other 875 servers in this category
- Published to the registry more recently than 42% of the other 875 servers in this category
- Basic checks equal to or better than 100% of the other 875 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is PlaywrightGen safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: Authorization
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Chrome DevTools MCP
by ChromeDevTools
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Runs on your computer★ 54,821Apache-2.0Updated 15 days ago
Install
MCP Server Browser
by bytedance
MCP server for browser use access
Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
PlaywrightGen
Playwright tests written from your real page, run until they pass, and kept as evidence a person approved.
Live at playwrightgen.com.
Writing a Playwright test is no longer the hard part — every editor has an assistant that will do it. What none of them keep is the thing an audit, a release decision or a customer actually asks for: which behaviour was agreed, by whom, at which version, and what the last run proved. That record is what this product is.
How it works
Two ways in, one chain.
The free tools need no account. Say what to test, paste a public URL, and PlaywrightGen reads the page, writes a test from its real accessibility tree, runs it in a remote browser, and fixes the failing step until it passes. You get working code and the run that proves it, signed so the evidence survives if you later bring it into a workspace. Nothing durable is claimed until you do.
The workspace turns that into a record:
- A Requirement is drafted, reviewed and approved. Approving writes an immutable version.
- Test Cases carry objective, steps and expected results, are approved the same way, and link to the Requirements they verify.
- Automation is generated from an approved Test Case version, validated against deterministic rules, proven on the live page, and then approved by a person — never by the generator and never by an agent.
- Run evidence arrives from your own CI. Your tests run on your runners, against your environment, with your secrets; only a bounded summary of results is sent. A
[pwg:...]marker in the test title is what ties a result to the approved version it is evidence for. - A proof link shares the result outside the team: a signed URL anybody can open, with an acceptance signature and a downloadable file they can keep.
Every claim on that chain names its source. A requirement with no passing test says so; a run that was skipped says it proved nothing; a report that was bounded says how much it did not cover.
What holds it honest
- A prompt is a request; a validator is a rule. Every promise a prompt makes has a deterministic check behind it: no focused tests, no fixed sleeps, no credentials in the file, no request to an address that is not the application under test, no Node capability a browser test has no business reaching for.
- A repair may not weaken a test. The quickest way to make a failing assertion pass is to delete it, so a fix that checks less than the test it was given is refused.
- Separation of duties. The person who proposed something cannot be the one who approves it; the MCP server can propose and send code and has no capability to approve, accept, share or delete, which a test enforces by reading the import graph.
- Every AI surface is measured.
npm run evalsgrades each prompt deterministically against structured output and compares the run with a hand-blessed baseline.
For agents (MCP)
PlaywrightGen is an MCP server, so Claude Code, Cursor or Copilot can read the approved intent instead of guessing: sixteen tools covering requirements, test cases, approved automation, recent failures, writing and proving a test on a live page, and proposing drafts for review. An agent gets exactly the rights of the person whose token it used.
Running it locally
npm installnpm run dev
Then npm run test:run for the suite, npm run typecheck, npm run lint, and npm run build. Integration tests need TEST_DATABASE_URL pointing at a database used for nothing else; they refuse anything that looks like production.
Built with Next.js, TypeScript, PostgreSQL (Prisma), Clerk, Tailwind, Playwright, OpenAI and Stripe.
Environment
Runtime:
DATABASE_URL— PostgreSQL for the application.DIRECT_URL— optional direct connection preferred by migration commands.TEST_DATABASE_URL— a separate database for integration tests. It never falls back to either of the above.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY,CLERK_SECRET_KEY,CLERK_WEBHOOK_SIGNING_SECRETOPENAI_API_KEY— server-only. Per-surface model overrides exist, for exampleOPENAI_REQUIREMENT_REVIEW_MODELandOPENAI_FAILURE_ANALYSIS_MODEL.UPSTASH_REDIS_REST_URL,UPSTASH_REDIS_REST_TOKEN— the per-minute and per-day AI allowances.RUNNER_INGEST_SECRET— signs live-run receipts, so a receipt proves a run of that exact code.BROWSERLESS_API_KEY— the remote browser the free tools and proving use.EXAMPLE_EVIDENCE_PROJECT_ID— optional: the one project whose evidence is published publicly at/proof/example.
GitHub integration (separate values per environment):
GITHUB_APP_ID,GITHUB_APP_PRIVATE_KEY,GITHUB_APP_SLUG,GITHUB_APP_CLIENT_ID,GITHUB_APP_CLIENT_SECRET,GITHUB_WEBHOOK_SECRETGITHUB_SETUP_STATE_SECRET— at least 32 characters, distinct from every other secret.NEXT_PUBLIC_APP_URL— the exact origin the GitHub callback returns to.
The App is held to a permission ceiling, checked on every installation and refused if exceeded: metadata: read, contents: read and write, pull_requests: read and write, issues: read. Contents write is what opens a pull request with approved test code; pull-requests write is what leaves the evidence note on it; issues read is what drafts a requirement from a ticket. User and installation tokens are transient and are never logged or stored.
Clerk webhooks go to /api/webhooks/clerk with CLERK_WEBHOOK_SIGNING_SECRET set locally and in the deployment, subscribed to:
user.created,user.updated,user.deletedorganization.created,organization.updated,organization.deletedorganizationMembership.created,organizationMembership.updated,organizationMembership.deleted
Local webhook delivery needs a secure tunnel to the local application. Never put a webhook secret in documentation or source control.
Operations
Reconcile one Clerk organization, dry-run by default:
npm run clerk:reconcile -- --organization-id org_exampleor
npm run clerk:reconcile -- --slug workspace-slug
Add --apply after reading the dry-run counts. It never sweeps every organization.
Database:
npm run prisma:formatnpm run prisma:validate npm run prisma:generate npm run prisma:migrate:dev npm run test:database
Never commit credentials, secrets, .env or .env.local. Never point a development migration or reset command at production.
Where the work is written down
docs/ROADMAP.md— what shipped, what is next, and what was deliberately not done.docs/DECISIONS.md— architecture decisions, each with its reason.docs/ARCHITECTURE.md,docs/PRODUCTION_READINESS.md— the shape of the system and the gates before a production deploy.examples/ci-proof— a disposable repository that proves the CI loop end to end.