apex-browser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APEX_BROWSER_PORT | No | Port for HTTP transport | 3010 |
| APEX_BROWSER_SHOTS | No | Directory for screenshots | /tmp |
| APEX_BROWSER_HEADLESS | No | Run headless: 1=headless, 0=headed | 0 |
| APEX_BROWSER_TRANSPORT | No | Transport mode: stdio or http | stdio |
| APEX_BROWSER_MAX_SESSIONS | No | Maximum number of concurrent browser sessions | 15 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_new_sessionA | Open an isolated browser session. engine: chrome (real Chrome) | chromium | webkit (Safari engine, multi) | safari (real Safari.app, single-session). Returns a session id. |
| browser_attachA | Attach to a Chrome already running with --remote-debugging-port. mode: default (adopt your logged-in session — real cookies) | isolated (fresh stealthed context on the same Chrome). Returns a session id usable with all other tools. |
| browser_navigateC | Go to a URL in a session. |
| browser_snapshotC | Title, URL, and indexed interactive elements (ref=e1,e2,...). Use a ref with click/type. |
| browser_clickC | Click an element by ref from the latest snapshot. |
| browser_typeC | Fill text into an element by ref; submit:true presses Enter. |
| browser_evaluateC | Run a JS expression in the page, return the result. |
| browser_screenshotC | Save a PNG of the current view, return its path. |
| browser_list_sessionsA | List all open sessions with engine and current URL. |
| browser_close_sessionC | Close and free a session. |
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 10 tools
Each tool has a distinct, non-overlapping purpose: session management, navigation, interaction, evaluation, and page capture. No two tools could be easily confused.
All tools use the consistent pattern 'browser_<action>' with snake_case, making them predictable and easy to understand.
10 tools is well-scoped for browser automation, covering the essential operations without being excessive or insufficient.
The set covers core actions (session creation, navigation, interaction, page inspection), though a few operations like back/forward or tab management are missing, but the surface is mostly adequate.