Quick Configuration
Choose the setup that matches your environment.
Before You Start
- Confirm you have the account, endpoint, or API key required for Playwright.
- Start with minimum scopes and read-only access where possible.
- Keep secrets in environment variables instead of hardcoding them in JSON.
This MCP does not have a tested config yet
Do not treat a generic endpoint placeholder as a real setup. Verify the official install path, command/url, env vars, and scopes first; if you already have sanitized config, run it through the checker.
Open config checkerCommon Pitfalls & Fixes
- ⚠️ Watch out: Headless browser dependencies and handling logins/consent screens safely.
- 🔑 Always store API keys in environment variables, never hardcode them in JSON.
- 🛡️ Start with read-only scopes if available to verify connection safely.
Example Prompts
Once connected, try these prompts to test capabilities:
- Open https://example.com, take a full-page screenshot, and extract the main headline.
- Navigate to a test form page, fill inputs, submit, and confirm success text.
- Click through a multi-step flow and summarize what changed on each step.
Verification Checklist
- Run 1-2 real prompts to confirm Playwright returns usable data.
- Check that error messages are clear enough for troubleshooting.
- Document the required scopes, dependencies, and env vars for future reuse.