MCP Browser 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
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 |
|---|---|
| launch_browserB | Launch a new browser instance (chromium, firefox, or webkit) |
| navigateC | Navigate to a URL |
| click_elementB | Click on an element by CSS selector |
| type_textB | Type text into an input field |
| screenshotC | Take a screenshot of the current page |
| get_element_textB | Get text content of an element |
| wait_for_elementC | Wait for an element to appear or disappear |
| evaluate_javascriptB | Execute JavaScript in the browser context |
| get_console_logsC | Get console logs from the browser |
| get_page_infoB | Get information about the current page |
| close_browserA | Close the current browser instance |
| analyze_screenshotB | Take a screenshot and analyze it with AI (Gemma3) to describe what is visible on the page |
| scrollC | Scroll the page in the specified direction |
| check_scrollabilityC | Check if the page is scrollable in the specified direction |
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 14 tools
Each tool has a clear, distinct purpose. Even similar tools like screenshot and analyze_screenshot are differentiated by the addition of AI analysis. No two tools overlap in functionality.
Most tools follow a verb_noun pattern (e.g., click_element, get_page_info). A few outliers like screenshot (noun used as verb) and navigate (verb only) introduce minor inconsistency, but the overall pattern is clear and predictable.
With 14 tools, the set covers the core browser automation tasks without being bloated. Each tool serves a specific purpose, and the count feels well-scoped for the domain.
The tool set covers essential browser operations: navigation, clicking, typing, scrolling, screenshots, JavaScript execution, and console logs. Minor gaps like form submission or cookie management are present but do not severely impact core workflows.