Skip to main content
Glama
RobithYusuf

MCP Camoufox

by RobithYusuf

browser_launch

Start a stealth browsing session and navigate to a URL, reusing cookies/localStorage across calls or using a clean temp profile to avoid account session collisions.

Instructions

Launch Camoufox stealth browser and navigate to URL. Browser persists between calls. By default cookies/localStorage persist in ~/.camoufox-mcp/profile. Set fresh_profile=true to start with a clean temp profile (auto-cleaned on browser_close) — useful when switching between accounts on the same domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to navigate toabout:blank
geoipNoAuto-detect timezone from IP
widthNoWINDOW width (0 = default 1280). The viewport matches this width and is 80px shorter than the window height (browser chrome) — use set_viewport_size to set a viewport independently of the window.
heightNoWINDOW height (0 = default 800). See width.
localeNoBrowser localeen-US
headlessNoRun without visible window
humanizeNoHuman-like mouse movements
no_viewportNoLet the content area follow the real OS window instead of a fixed viewport (Playwright viewport:null). WARNING: this drops the window-size cap, so the viewport can end up LARGER than the spoofed screen — a window wider than its own screen is an easy anti-bot tell. Prefer set_viewport_size unless you need a full-window canvas.
fresh_profileNoStart with a clean temp profile (no carry-over cookies/cache). Temp dir is removed when browser_close is called. Use when switching between accounts on the same domain to avoid login session collisions.
Install Server

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses key behaviors beyond the schema: browser persistence, default profile path (~/.camoufox-mcp/profile), and auto-cleaning of temp profiles on browser_close. It does not mention side effects like visible windows when headless=false, but that is covered in the schema. Overall, it adds meaningful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficient and front-loaded: the first sentence states the action, the second explains persistence, and the third covers the fresh-profile option. Every sentence earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main behavioral aspects needed to use the tool correctly: persistence, profile handling, and a key use case for fresh_profile. The schema covers all 9 parameters in detail, so the description doesn't need to repeat them. A minor gap is ambiguity about calling browser_launch again when a browser already exists, but overall it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each parameter is already well-documented, so the baseline is 3. The description adds minor extra context (e.g., the default profile path and account-switching use case) but does not significantly expand on the parameter meanings beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Launch Camoufox stealth browser and navigate to URL.' It clearly defines the tool's core purpose and distinguishes it from navigation/other sibling tools by being the launcher. The phrase 'Browser persists between calls' further clarifies its role as the session initiator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use the tool: it launches a browser and persists between calls, implying it should be used once at the start of a session. It also provides practical guidance on when to set fresh_profile=true (switching between accounts on the same domain). It does not explicitly name alternatives or state when-not-to-use, but the context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RobithYusuf/mcp-camoufox'

If you have feedback or need assistance with the MCP directory API, please join our Discord server