Skip to main content
Glama
KvFxKaido

Browser Instrumentation MCP Server

by KvFxKaido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
browser_session_createA

Create a new browser session for observation.

Sessions start in observation-only mode. Actions require explicit escalation.

Args:
    name: Unique name for the session (e.g., "main", "test-session")
    headless: If True, run browser without visible window
    viewport_width: Browser viewport width in pixels (default: 1280)
    viewport_height: Browser viewport height in pixels (default: 720)

Returns:
    Confirmation message with session name and status
browser_session_connectA

Connect to an existing browser session over CDP.

Sessions start in observation-only mode. Actions require explicit escalation.

Args:
    name: Unique name for the session (e.g., "main", "test-session")
    cdp_url: CDP websocket URL (e.g., ws://127.0.0.1:9222/devtools/browser/...)

Returns:
    Confirmation message with session name and status
browser_session_listB

List all browser sessions with their status.

Returns:
    List of sessions showing name, status (active/escalated), and current URL
browser_session_destroyA

Destroy a browser session and clean up resources.

Args:
    name: Name of the session to destroy

Returns:
    Confirmation message
browser_session_escalateA

Escalate a session to allow action tools (click, type, execute).

WARNING: This enables side effects. Actions will be logged.

Args:
    name: Name of the session to escalate
    reason: Justification for why actions are needed

Returns:
    Warning message and confirmation
browser_inspect_navigateA

Navigate to a URL for observation.

Navigation is considered an inspect operation because it sets up
what you want to observe.

Args:
    session: Name of the browser session
    url: URL to navigate to (https:// added if no protocol specified)

Returns:
    The page title and final URL after navigation
browser_inspect_screenshotA

Take a screenshot of the current page.

Args:
    session: Name of the browser session
    full_page: If True, capture the entire scrollable page

Returns:
    Base64-encoded PNG screenshot with data URI prefix
browser_inspect_domA

Get DOM HTML content from the page.

Args:
    session: Name of the browser session
    selector: Optional CSS selector to get specific element's HTML

Returns:
    HTML content (truncated if over 100KB)
browser_inspect_textA

Get text content from the page (no HTML tags).

Args:
    session: Name of the browser session
    selector: Optional CSS selector to get specific element's text

Returns:
    Text content of the page or element
browser_inspect_consoleB

Get captured console log messages from the page.

Args:
    session: Name of the browser session

Returns:
    JSON array of console entries with level, message, and timestamp
browser_inspect_networkA

Get captured network requests from the page.

Args:
    session: Name of the browser session

Returns:
    JSON array of network entries with method, url, status, and timestamp
browser_inspect_eventsA

Get the event log for a session.

The event log is append-only and records all tool calls made to this session.

Args:
    session: Name of the browser session

Returns:
    JSON array of all events in chronological order
browser_act_clickA

Click an element on the page.

REQUIRES: Session must be escalated first via browser_session_escalate.

Args:
    session: Name of the browser session
    selector: CSS selector for the element to click
    reason: Justification for why this click is necessary

Returns:
    Observed changes after the click (NOT success/failure)
browser_act_typeA

Type text into an input element.

REQUIRES: Session must be escalated first via browser_session_escalate.

Args:
    session: Name of the browser session
    selector: CSS selector for the input element
    text: Text to type
    reason: Justification for why this input is necessary
    clear_first: If True, clear the input before typing

Returns:
    Observed changes after typing (NOT success/failure)
browser_act_executeA

Execute JavaScript in the browser context.

REQUIRES: Session must be escalated first via browser_session_escalate.

Args:
    session: Name of the browser session
    script: JavaScript code to execute
    reason: Justification for why this script is necessary

Returns:
    Observed changes after execution (NOT success/failure)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 15 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. The tools are cleanly divided into 'act' (click, execute, type), 'inspect' (console, dom, events, navigate, network, screenshot, text), and 'session' (connect, create, destroy, escalate, list) categories, each targeting specific browser automation tasks. The descriptions reinforce these distinctions, making misselection unlikely.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern with a clear prefix structure: 'browser_act_*' for actions, 'browser_inspect_*' for inspection, and 'browser_session_*' for session management. All names use snake_case consistently, and the verb choices (click, execute, type, inspect, connect, create, etc.) are predictable and well-aligned with their functions.

Tool Count5/5

The 15 tools are well-scoped for a browser instrumentation server, covering all essential aspects: session lifecycle management, page inspection, and user interactions. Each tool earns its place without redundancy, and the count is typical for this domain (similar to the GitHub example with 10 tools). No tools feel unnecessary or missing for the core purpose.

Completeness5/5

The tool surface provides complete coverage for browser automation. It includes session CRUD (create, connect, list, destroy), escalation for actions, comprehensive inspection (dom, text, console, network, events, screenshot, navigation), and core user actions (click, type, execute). There are no obvious gaps; agents can perform full observation and interaction workflows without dead ends.

Resources