SmartBrowserMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | info |
| MCP_TRANSPORT | No | Transport mode - stdio or http | stdio |
| BROWSER_SLOW_MO | No | Slow down operations by specified milliseconds | 0 |
| BROWSER_TIMEOUT | No | Browser operation timeout in milliseconds | 30000 |
| MCP_SERVER_HOST | No | Server host | 0.0.0.0 |
| MCP_SERVER_PORT | No | Server port | 3000 |
| BROWSER_HEADLESS | No | Run browser in headless mode | true |
| PLAYWRIGHT_BROWSERS_PATH | No | Custom path to Playwright browsers |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_taskC | Execute any task on a website using natural language instructions |
| check_consoleA | Get filtered console messages by level |
| check_networkC | Monitor filtered network requests |
| take_screenshotC | Capture screenshot with viewport options |
| generate_reportC | Create execution summary with metrics |
| clear_sessionB | Clean up all browser data securely |
| get_page_contentA | Extract text content from the page or a specific element. Returns readable text content for verification and analysis. |
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 7 tools
Each tool targets a distinct browser function: console messages, network requests, session cleanup, task execution, report generation, page content extraction, and screenshots. No overlap in purpose.
All tool names follow a consistent verb_noun pattern with underscores (check_console, clear_session, execute_task, etc.). No mixing of styles.
7 tools is well-scoped for a browser automation server. Each tool provides a distinct capability without redundancy or excess.
Covers core browser automation needs: monitoring, content extraction, screenshots, session management, and reporting. Minor gaps like explicit navigation controls, but execute_task likely handles them via natural language.