Which providers does Parallel Browser Mcp support?
It supports four providers: Playwright (local Chromium), Browserbase (via `@browserbasehq/sdk`), Anchor (via `anchorbrowser`), and Cloudflare (via Cloudflare Browser Run).
@etairl
基本情報
MCP server for parallel browser automation across multiple providers. Run multiple concurrent browser sessions in memory with a shared, provider-agnostic tool surface across Playwright (local Chromium), Browserbase, Anchor Browser, and Cloudflare Browser Run. Each session gets a
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"parallel-browser-mcp": {
"command": "npx",
"args": [
"parallel-browser-mcp@latest"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。
Parallel Browser Mcp is an MCP server for parallel browser automation. It exposes a numeric session model so one client can create and control multiple browser sessions simultaneously across several providers: local Playwright Chromium, Browserbase, Anchor Browser, and Cloudflare Browser Run. It is designed for developers building AI-driven browser automation workflows within MCP‑compatible clients.
Install via npm (npx parallel-browser-mcp@latest) and add the server configuration to your MCP client (e.g., Claude, Cursor, VS Code). The server runs over stdio. Create sessions by calling start_session with a provider, then use any browser_* tool by passing the returned numeric sessionId. Provider credentials and defaults are set in environment variables or a JSON config object.
It supports four providers: Playwright (local Chromium), Browserbase (via `@browserbasehq/sdk`), Anchor (via `anchorbrowser`), and Cloudflare (via Cloudflare Browser Run).
Credentials are set via environment variables: `BROWSERBASE_API_KEY`, `ANCHOR_API_KEY`, `CLOUDFLARE_API_TOKEN`, and `CLOUDFLARE_ACCOUNT_ID`. Playwright requires no credentials. Additional provider‑specific options can be set in a JSON configuration provided through `BROWSER_MCP_CONFIG` or a config file.
You can run it locally with `node dist/index.js` after building, or use the npm CLI: `npx parallel-browser-mcp@latest`. The server communicates over stdio, so it integrates with any MCP client that supports stdio transport.
The server offers session tools (`start_session`, `close_session`, `close_all_sessions`, `get_sessions`) and browser tools such as `browser_navigate`, `browser_click`, `browser_fill`, `browser_screenshot`, `browser_snapshot`, `browser_evaluate`, and more—over 20 in total.
Call `start_session` with a provider name (e.g., `"playwright"`). The response includes a numeric session ID. Then call any `browser_*` tool with `{ "sessionId": <id>, ...}`. Finally, call `close_session` to release resources.
This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.
Give your AI agent the live web. One MCP server for Search, Fetch, Browser, and Agent: browse real sites, extract structured data, fill forms, and run multi-step workflows. Search and Fetch are free.
Playwright MCP server
Let Claude Code, Claude Desktop, OpenAI Codex, Kimi and any MCP-capable AI agent create, launch, check and drive browser profiles in Nullprint, the AI antidetect browser. Install with one command.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
コメント