@codeinklingon/browser-mcp
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 |
|---|---|
| browser_tab_openC | Open a browser tab, optionally navigating to a URL. Reuses existing tab by name. |
| browser_tab_runA | Execute JavaScript code in the browser tab. The code runs as an async function body. CRITICAL RULES:
Available variables in scope:
ElementHandleActions: { click, type, fill, hover, focus, screenshot, evaluate, scrollIntoView }
Selectors: CSS by default, "text/Sign in" for visible text, "xpath/...", "aria-ref=e5" from ariaSnapshot. Single-expression code auto-returns its value (no explicit 'return' needed). Use display() for intermediate values. |
| browser_tab_closeA | Close the browser tab and release resources. |
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 3 tools
Each tool has a distinct action: open, run, close. No overlap; an agent can easily select the correct tool for each step of the browser lifecycle.
All names follow the exact pattern `browser_tab_<verb>`, with verbs being clear actions. Perfectly consistent.
Three tools cover the essential browser tab lifecycle: open, execute code, close. This is a well-scoped set for the server's purpose.
The tools cover the primary workflow (open, run, close). While additional tools for specialized actions (e.g., tab navigation) could be added, the API methods described in the critical rules provide sufficient interactivity, so no dead ends.