camoufox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY | No | Proxy server URL (http/socks5) | |
| HEADED | No | Show browser window (true/false) | false |
| LOCALE | No | Browser locale (e.g., en-US) | |
| HUMANIZE | No | Cursor movement intensity (0-2) | 1 |
| NO_GEOIP | No | Disable geolocation spoofing (true/false) | false |
| BLOCK_IMAGES | No | Block image loading (true/false) | false |
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 |
|---|---|
| browser_navigateC | Navigate to a URL |
| browser_snapshotA | Get accessibility snapshot of the current page. Returns element refs (e.g., e0, e1) for interactions. |
| browser_clickC | Click an element by its ref from the snapshot |
| browser_typeA | Type text into an element (appends to existing) |
| browser_fillC | Fill text into an element (clears first) |
| browser_hoverC | Hover over an element |
| browser_select_optionB | Select option(s) in a dropdown |
| browser_press_keyC | Press a keyboard key |
| browser_wait_forB | Wait for text or a specified time |
| browser_evaluateB | Evaluate JavaScript in the page context |
| browser_screenshotA | Take a screenshot of the current page |
| browser_tabsC | Manage browser tabs: list, new, close, or select |
| browser_navigate_backA | Go back to the previous page |
| browser_closeC | Close the browser |
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 14 tools
Each tool has a clearly distinct action: navigate, snapshot, click, type, fill, hover, select, key press, wait, evaluate, screenshot, tabs, back, close. The only potential overlap is type vs. fill, but descriptions clarify that fill clears first, making them distinct.
All tools use the 'browser_' prefix followed by a verb_noun pattern (e.g., browser_navigate, browser_click, browser_screenshot). The naming is predictable and uniform, with only minor deviations like browser_wait_for (verb_preposition) and browser_tabs (verb_noun but plural) that are still clear.
14 tools is an ideal size for a browser automation server. It covers all essential interactions without being bloated. Each tool serves a specific purpose and there are no redundant or unnecessary tools.
The tool set covers the core browser automation lifecycle: navigation, interaction, tab management, screenshots, and JavaScript evaluation. Minor gaps exist, such as the absence of navigate_forward (only back) and a dedicated wait-for-element function (only wait for text or time). These are small but notable omissions.