Browser Intelligence 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| take_screenshotA | Captures a PNG screenshot of any URL using a real headless browser. Returns the image as a base64-encoded string. Use fullPage=true to capture the entire scrollable page. |
| scrape_pageA | Navigates to a URL with a real browser and extracts structured content: page title, meta description, visible body text (first 5000 chars), and up to 30 links. Optionally provide a CSS selector to extract a specific element's text. |
| run_visual_testB | Runs a set of visual checks against a URL using a real browser. Supported check types: 'has_text' (text appears on page), 'has_element' (CSS selector exists), 'title_contains' (page title contains value), 'status_ok' (HTTP response is 2xx/3xx). Returns a detailed pass/fail report for each check. |
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 clear, non-overlapping purpose: take_screenshot captures visual state, scrape_page extracts content and links, and run_visual_test performs assertion-based checks. No ambiguity in usage.
All three tools follow a consistent verb_noun pattern (take_screenshot, scrape_page, run_visual_test) with clear, descriptive verbs. Naming is uniform and predictable.
With 3 tools, the set is minimal but well-scoped for a focused browser intelligence server. Each tool serves a distinct core function (capturing, extracting, testing) and earns its place without unnecessary bloat.
The surface covers the primary browser intelligence workflows (screenshot, scrape, and visual checks). Minor gaps exist—such as no support for full HTML extraction or waiting for dynamic content—but for the stated purpose, the coverage is solid and workable.