PlaywrightGen MCP server
Commit Nov 14, 2026Allows AI agents to read approved requirements, generate Playwright automation, and manage test evidence within an editor.
Also known as hmamut39/playwrightgen
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Nov 14, 2026
- License
- —
What is PlaywrightGen MCP?
PlaywrightGen allows AI agents to read approved requirements, generate Playwright automation, and manage test evidence within an editor.
Summary generated from the project's README
About PlaywrightGen MCP server
PlaywrightGen provides a structured way for AI agents to manage the entire lifecycle of browser automation. It connects requirements, test cases, and actual code to create a verifiable chain of evidence for audits or release decisions. Developers using AI clients like Claude Code, Cursor, or Copilot can use this server to read approved intent rather than guessing what to test. The server includes sixteen tools that allow agents to handle requirements, manage test cases, propose automation drafts, and analyze recent failures.
To function, the server requires several configurations including a PostgreSQL database, OpenAI API keys, and Clerk authentication. It also utilizes Browserless for remote browser execution and Upstash Redis for managing AI allowances. When integrated with GitHub, it can draft requirements from issues and open pull requests with approved test code. The system enforces strict separation of duties, ensuring that an agent can propose code but lacks the capability to approve or delete the records it creates.
What you can do with it
- 1Generate automation from requirementsAn AI agent can read an approved requirement and propose a draft test case for review.
- 2Verify tests against live pagesThe system can read a public URL and write a Playwright test based on the actual accessibility tree.
- 3Automate documentation from GitHub issuesThe server can use GitHub integration to turn a ticket into a formal requirement.
- 4Maintain an audit trailDevelopers can link CI test results back to specific approved versions of a test.
Written from the project's README. Every use case is checked against a quote from it.
How to install PlaywrightGen MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall PlaywrightGen MCP in Claude Code
$ claude mcp add --transport http playwrightgen https://playwrightgen.com/api/mcpInstall PlaywrightGen MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"playwrightgen": {
"url": "https://playwrightgen.com/api/mcp"
}
}
}Install PlaywrightGen MCP in VS Code
.vscode/mcp.json
{
"servers": {
"playwrightgen": {
"type": "http",
"url": "https://playwrightgen.com/api/mcp"
}
}
}Install PlaywrightGen MCP in VS Code CLI
$ code --add-mcp '{"name":"playwrightgen","type":"http","url":"https://playwrightgen.com/api/mcp"}'Install PlaywrightGen MCP in Codex
$ codex mcp add playwrightgen --url https://playwrightgen.com/api/mcpInstall PlaywrightGen MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.playwrightgen] url = "https://playwrightgen.com/api/mcp"
Install PlaywrightGen MCP in Gemini CLI
$ gemini mcp add -s user --transport http playwrightgen https://playwrightgen.com/api/mcpInstall PlaywrightGen MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"playwrightgen": {
"url": "https://playwrightgen.com/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablehmamut39/playwrightgen is public and reachablegithub.com/hmamut39/playwrightgen ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-14github.com/hmamut39/playwrightgen ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubPlaywrightGen
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 install
npm 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_example
# or
npm run clerk:reconcile -- --slug workspace-slug
Add --apply after reading the dry-run counts. It never sweeps every
organization.
Database:
npm run prisma:format
npm 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.
PlaywrightGen MCP questions
How do I add PlaywrightGen MCP to Claude Code?
Run claude mcp add --transport http playwrightgen https://playwrightgen.com/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add PlaywrightGen MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can an AI agent do with this MCP server?
An agent can use sixteen tools to manage requirements, test cases, approved automation, recent failures, and propose drafts for review.
Can the AI agent approve tests?
No, the MCP server is restricted from approving, accepting, sharing, or deleting tests to maintain separation of duties.
How does the system ensure test quality?
It uses deterministic validators to prevent issues like fixed sleeps or hardcoded credentials, and refuses repairs that weaken assertions.