How do I use Browser CDP MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. 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

by Myestery

Overview Schema Related Servers Score Discussions

JavaScript

Local

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_send
Screenshot 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: Chrome DevTools MCP

Installation

npm install

Usage

npm start

The 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 user

Skill Integration

Add the browser skill to claude:

cp .path/to/browser-tool/.claude/skills/browser.md ~/.claude/skills/browser.md

Dependencies

@modelcontextprotocol/sdk - MCP SDK for server implementation
playwright - Browser automation
zod - Schema validation

License

MIT

Available Tools

4 tools

cdp_sendD

ParametersJSON Schema

Name	Required	Description	Default
`method`	Yes	CDP method (e.g., 'Page.navigate', 'DOM.getDocument', 'Runtime.evaluate')
`params`	No	Parameters object for the CDP method

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

close_browserD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_urlD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

screenshotD

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	Image format
`fullPage`	No	Capture full scrollable page

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesJan 1, 2026
- First observedcdp_send
- First observedclose_browser
- First observedget_url
- First observedscreenshot

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0

Disambiguation5/5

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.

Naming Consistency3/5

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.

Tool Count3/5

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.

Completeness2/5

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

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Remote Browser MCP Server from MCPBundlesOAuth
com.mcpbundles
Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video
Browser Automation Code Execution
2
browser-mcp
io.github.Shreyas-Profile
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Browser Automation Web Scraping
2
render-mcp A
io.github.RodRomer
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.
61
agent-web-actions
com.trycloudflare.clients-involving-billion-headers
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
Browser Automation Web Scraping
2

Related MCP Servers

Chrome DevTools MCP
Browser Automation Web Scraping Testing & QA Tools
ctrlShiftBryan
A
license
Not graded
quality
D
maintenance
Enables AI coding assistants to control and inspect a live Chrome browser through DevTools for automated testing, performance analysis, debugging, and web scraping. Provides reliable browser automation using Puppeteer with comprehensive DevTools access.
Updated 9 months ago (2025-12-21 01:07 UTC)
3,288,165
3
Apache 2.0
Chrome DevTools MCP
Browser Automation Web Scraping Developer Tools
Anirbandz
A
license
Not graded
quality
D
maintenance
Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.
Updated 8 months ago (2026-01-11 01:04 UTC)
3,288,165
Apache 2.0
superpowers-chrome
Browser Automation Web Scraping
obra
A
license
A
quality
A
maintenance
Enables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.
Updated a month ago (2026-08-07 19:41 UTC)
1
346
MIT
browser-devtools-mcp
Browser Automation Web Scraping
kikcmime
A
license
Not graded
quality
C
maintenance
Enables reading browser DevTools data (tabs, console errors, network requests, screenshots, DOM, CSS, JS execution) via Chrome DevTools Protocol.
Updated 2 months ago (2026-06-25 09:22 UTC)
5,218
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Myestery/browser-cdp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server