# Browserbase vs Playwright MCP

The deciding difference is operational: Playwright MCP can run on infrastructure you control, Browserbase cannot. If that constraint is real for you, it settles the choice before anything else is considered.

| | Browserbase | Playwright MCP |
| --- | --- | --- |
| Licence | Proprietary | Open source |
| Pricing | freemium | open source |
| Self-hostable | No | Yes |
| Languages | TypeScript, Python | TypeScript |
| Install | — | npm install -g @playwright/mcp |
| Keys required | BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID | None |

## Full pages

- https://newagent.build/c/browserbase
- https://newagent.build/c/playwright-mcp

## Machine interfaces

- `GET https://newagent.build/api/registry` — every component as JSON
- `GET https://newagent.build/api/vendors` — vendors, with the repo and releases feed to watch
- `GET https://newagent.build/api/advise?q=<plain english>` — recommended stack for a description
- `GET https://newagent.build/api/stack?<layer>=<id>&format=sh|json|md|yml|agents|env` — a stack as files
- `GET https://newagent.build/llms.txt` — the whole registry in one fetch

Any page here also returns markdown if you send `Accept: text/markdown`.