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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/perception30/browser-connect-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server