Browser CDP MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Browser CDP MCP Server take a screenshot of the current page and save it as a PNG"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Browser CDP MCP Server
A minimal MCP (Model Context Protocol) server that provides direct access to the Chrome DevTools Protocol (CDP) for maximum flexibility browser control.
Features
Raw CDP Access: Call any Chrome DevTools Protocol method directly via
cdp_sendScreenshot Capture: Take screenshots in PNG or JPEG format
URL Retrieval: Get the current page URL
Browser Management: Launch and close browser instances
Related MCP server: browser-devtools-mcp
Installation
npm installUsage
npm startThe server communicates over stdio using the MCP protocol.
Tools
cdp_send
Execute any CDP method. Reference: https://chromedevtools.github.io/devtools-protocol/
Parameters:
method(string): CDP method name (e.g.,Page.navigate,DOM.getDocument,Runtime.evaluate)params(object, optional): Parameters for the CDP method
Example:
{
"method": "Page.navigate",
"params": { "url": "https://example.com" }
}screenshot
Capture a screenshot of the current page.
Parameters:
format(string, optional):"png"or"jpeg"(default:"png")fullPage(boolean, optional): Capture full scrollable page (default:false)
get_url
Returns the current page URL.
close_browser
Closes the browser instance and cleans up resources.
MCP Configuration
Add to your MCP client configuration:
claude mcp add-json browser '{
"type": "stdio",
"command": "node",
"args": ["path/to/browser-tool/server.js"]
}' --scope userSkill Integration
Add the browser skill to claude:
cp .path/to/browser-tool/.claude/skills/browser.md ~/.claude/skills/browser.mdDependencies
@modelcontextprotocol/sdk- MCP SDK for server implementationplaywright- Browser automationzod- Schema validation
License
MIT
Available Tools
4 toolscdp_sendD
Inputs: method (required), params.
close_browserD
Inputs: no named parameters.
get_urlD
Inputs: no named parameters.
screenshotD
Inputs: format, fullPage.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: cdp_send appears to send commands to the Chrome DevTools Protocol, close_browser terminates the browser session, get_url retrieves the current URL, and screenshot captures a visual snapshot. There is no overlap in functionality between these tools.
The naming is mixed: cdp_send uses a prefix-based convention, while close_browser, get_url, and screenshot follow a verb_noun pattern. This inconsistency reduces predictability, but all names are still readable and descriptive of their functions.
With only 4 tools, the set feels thin for a browser automation server, lacking common operations like navigation, clicking, or input handling. However, the tools cover basic session management and inspection, making it borderline appropriate for minimal use cases.
The toolset is severely incomplete for browser automation: it lacks essential actions like navigate, click, type, or evaluate JavaScript, and there is no coverage for interacting with page elements or handling events. This will cause significant agent failures in typical browsing tasks.
Maintenance
Related MCP Connectors
Cloud browser, web extraction, screenshots, and remote CDP tools for AI agents.
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Undetectable cloud browser sessions for AI agents and scrapers. Navigate, extract, click, captcha.
Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.1372MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading browser DevTools data (tabs, console errors, network requests, screenshots, DOM, CSS, JS execution) via Chrome DevTools Protocol.5,213 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceLets coding agents control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis. Provides access to Chrome DevTools capabilities such as tracing, network inspection, screenshots, and console messages through MCP clients.2,405,354 npmApache 2.0