Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort the auth gate binds to. Default: 10000.
MCP_TOKENYesRequired. Bearer token every request must present. The container refuses to start without it.
UPSTREAM_PORTNoLoopback port the MCP server listens on behind the gate. Default: 8931.
PLAYWRIGHT_MCP_ALLOWED_HOSTSNoOptional comma-separated allowed hosts for the host check; needed when using a custom domain.

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
browser_closeB

Close the page

browser_resizeB

Resize the browser window

browser_console_messagesB

Returns all console messages

browser_handle_dialogC

Handle a dialog

browser_evaluateB

Evaluate JavaScript expression on page or element

browser_file_uploadB

Upload one or multiple files

browser_dropA

Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.

browser_fill_formB

Fill multiple form fields

browser_press_keyB

Press a key on the keyboard

browser_typeB

Type text into editable element

browser_navigateC

Navigate to a URL

browser_navigate_backA

Go back to the previous page in the history

browser_network_requestsA

Returns a numbered list of network requests since loading the page. Use browser_network_request with the number to get full details.

browser_network_requestA

Returns full details (headers and body) of a single network request, or a single part if part is set. Use the number from browser_network_requests.

browser_run_code_unsafeA

Run a Playwright code snippet. Unsafe: executes arbitrary JavaScript in the Playwright server process and is RCE-equivalent.

browser_take_screenshotA

Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.

browser_snapshotB

Capture accessibility snapshot of the current page, this is better than screenshot

browser_clickB

Perform click on a web page

browser_dragA

Perform drag and drop between two elements

browser_hoverA

Hover over element on page

browser_select_optionB

Select an option in a dropdown

browser_tabsA

List, create, close, or select a browser tab.

browser_wait_forA

Wait for text to appear or disappear or a specified time to pass

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 23 tools

Disambiguation4/5

Most tools target distinct browser actions (click, type, hover, drag, drop, etc.), and descriptions clarify edge cases like snapshot vs screenshot. However, browser_drag vs browser_drop and browser_type vs browser_press_key could still cause occasional misselection without careful reading.

Naming Consistency3/5

All tools share a consistent browser_ prefix and snake_case style, but the action part is mixed: verbs (browser_close, browser_evaluate) coexist with nouns (browser_snapshot, browser_network_requests, browser_tabs). This is readable but not a uniform verb_noun pattern.

Tool Count4/5

23 tools is on the heavier side but justified for a full-featured browser automation server covering navigation, input, inspection, network, tabs, and dialogs. A few tools like browser_network_requests/request could arguably be merged, but the count is not excessive.

Completeness4/5

The toolset covers most core browser automation workflows, including navigation, clicking, typing, forms, screenshots, and network inspection. Minor gaps like dedicated checkbox/radio interaction or page reload are missing, but agents can work around them via browser_click or browser_evaluate.

Maintenance

ActivityMaintained
ResponsivenessNo issues