Cdp Bridge MCP Server

Cdp Bridge MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Cdp Bridge MCP directly instead of describing what you should do. CDP Bridge MCP 是一个连接 MCP 客户端与真实浏览器会话的桥接服务，通过配套的 Chromium 插件接入浏览器页面，让任何大模型客户端都可以丝滑、轻易地读取标签页、扫描页面、执行自动化操作、截图和导航。.

What the assistant can call

Once Cdp Bridge MCP is connected, these are the calls the assistant has available:

• browser_get_tabs — 无
• browser_scan — tabs_only (bool), switch_tab_id (str), text_only (bool)
• browser_execute_js — script (str, 必填), switch_tab_id (str), no_monitor (bool)
• browser_switch_tab — tab_id (str, 必填)
• browser_focus_tab — tab_id (str, 必填)
• browser_batch — commands (list[dict], 必填), tab_id (str), timeout (float)
• browser_wait — condition_js (str, 必填), timeout (float), interval (float), switch_tab_id (str)
• browser_navigate — url (str, 必填)
• browser_screenshot — tab_id (str)
• browser_save_image — screenshot_json_str_or_file (str, 必填), output_path (str)
• streamable-http — 服务以独立 HTTP 进程运行，客户端通过 HTTP 请求连接
• Codex — The Codex tool exposed by this server

Setting it up

cdp-bridge on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 3 environment variables: ANTHROPIC_API_KEY, ANTHROPIC_BASE_URL, ANTHROPIC_MODEL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cdp Bridge MCP's toolset — browser_get_tabs, browser_scan, browser_execute_js and 11 more — is a fair guide to whether it matches your workflow. It is maintained by unagi-cq; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cdp Bridge MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cdp bridge mcp mcp server does with a few real requests.