wsl-chrome-mcp-bridge
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrome_openA | Launch Chrome with remote debugging and connect DevTools MCP. Call this before using any other Chrome DevTools tools. |
| chrome_closeA | Close the Chrome debugging instance and disconnect DevTools MCP. |
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 2 tools
The two tools, chrome_open and chrome_close, are completely distinct actions with no overlap. Each serves a single clear purpose.
Both tools follow the consistent pattern 'chrome_<verb>', using snake_case and clear verb_noun structure.
With exactly two tools for opening and closing the bridge, the count is minimal but perfectly scoped for the server's intended role.
The tool set fully covers the lifecycle of the Chrome debugging instance (start and stop), with no necessary operations missing for this narrow domain.