Browser CDP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cdp_sendD | – |
| screenshotD | – |
| get_urlD | – |
| close_browserD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.