browser-connect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level for the MCP server. | info |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_list_tabsA | List all available browser tabs that can be connected to |
| browser_connectB | Connect to a specific browser tab for debugging |
| browser_disconnectC | Disconnect from a specific browser tab |
| console_searchA | Search and filter console messages from connected browser tabs |
| network_analyzeC | Analyze network requests and responses from connected browser tabs |
| network_performanceC | Get network performance statistics for a connected browser tab |
| browser_launchB | Launch a new browser instance with debugging enabled |
| network_export_harB | Export network traffic to HAR (HTTP Archive) format |
| console_advanced_searchB | Advanced console search with pattern matching, correlation, and statistics |
| performance_profileC | Advanced performance profiling with bottleneck detection and recommendations |
| error_correlateA | Automatically correlate errors between console and network, find root causes |
| security_scanC | Scan for security vulnerabilities in console and network traffic |
| log_analyzeC | Intelligently analyze logs to find patterns, anomalies, trends, and suggestions |
| debug_localhostA | Launch browser with a localhost URL and automatically connect for debugging |
| backend_logs_streamB | Stream and search logs from backend applications (files, processes, Docker containers) |
| backend_debugger_attachB | Attach to a Node.js process debugger for breakpoint debugging |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find_javascript_errors | Find and analyze JavaScript errors in the console |
| debug_failed_api_calls | Debug failed API calls and network errors |
| analyze_slow_page_load | Analyze slow page load performance |
| debug_memory_leaks | Detect potential memory leaks from console patterns |
| security_audit | Basic security audit of console and network |
| debug_cors_issues | Debug Cross-Origin Resource Sharing (CORS) issues |
| analyze_render_performance | Analyze rendering and paint performance issues |
| debug_websocket_issues | Debug WebSocket connection problems |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Multiple tools have overlapping purposes: console_search and console_advanced_search are nearly identical, network_performance and performance_profile both cover performance metrics, and log_analyze and backend_logs_stream both deal with log analysis. This creates confusion about which tool to select for a given task.
Tool names use a mix of prefixes and patterns: browser_list_tabs and browser_connect follow verb_noun, but network_performance is a noun, performance_profile is a noun, and debug_localhost uses a different prefix. Prefixes are inconsistent (some tools have no domain prefix).
16 tools is slightly above the typical 3-15 range, but the broad scope covering browser debugging, network analysis, performance profiling, security scanning, and backend logging justifies the count. Each tool has a distinct role, even if a few could be consolidated.
The tool set covers core debugging workflows like connecting, analyzing network/console, and exporting HAR, but lacks general browser interaction (e.g., navigation, DOM inspection, JavaScript execution) and tab management (closing tabs). Some important lifecycle operations are missing.