atlas-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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateB | Navigate to a URL and return a screenshot with labeled interactive elements |
| screenshotB | Take a screenshot of the current page with labeled elements |
| clickC | Click on an element by its label ID (shown as [N] on the screenshot) |
| multi_clickB | Click multiple elements at once (useful for CAPTCHA, checkboxes, etc.) |
| typeA | Type text at the current focus position |
| scrollC | Scroll the page up or down |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: click targets single elements, multi_click handles multiple elements, navigate loads pages, screenshot captures the current state, scroll moves the viewport, and type inputs text. The descriptions make it easy for an agent to choose the right tool for each interaction.
All tool names follow a consistent snake_case pattern with clear, imperative verbs (click, navigate, screenshot, scroll, type) and a descriptive multi_click variant. There are no deviations in style or convention, making the set predictable and readable.
With 6 tools, the server is well-scoped for browser automation, covering core interactions like navigation, clicking, typing, scrolling, and screenshot capture. Each tool earns its place without redundancy, fitting a typical range for this domain.
The toolset covers essential browser actions (navigation, interaction, viewing) effectively, with no obvious dead ends. A minor gap exists in more advanced interactions like hovering, drag-and-drop, or form submission, but agents can work around this using the provided tools for most common tasks.