camofox-mcp

create_tab

Create a new browser tab with anti-detection fingerprinting. Each tab gets a unique fingerprint. Optionally provide a URL, userId, sessionKey, and viewport.

Instructions

Create a new browser tab with anti-detection fingerprinting. Each tab gets a unique fingerprint. Optionally provide a URL, userId, sessionKey, and viewport. To share the camofox CLI default browser profile/context, pass userId "cli-default" and sessionKey "default"; this creates a tracked MCP tab in that context but does not attach to a CLI tab that is already open.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Full URL including protocol (e.g. 'https://example.com')
`proxy`	No	Raw proxy override. proxyProfile takes precedence when both are provided.
`locale`	No	BCP 47 locale override (e.g. "ja-JP", "vi-VN")
`preset`	No	Named geo preset (e.g. "us-east", "us-west", "japan", "uk", "germany", "vietnam", "singapore", "australia"). Sets locale, timezone, and geolocation.
`userId`	No	User ID for session isolation. MCP defaults to CAMOFOX_DEFAULT_USER_ID/default; use "cli-default" with sessionKey "default" to share the camofox CLI default context.
`geoMode`	No	Geo merge mode. explicit-wins keeps explicit locale/timezone/geolocation; proxy-locked requires proxy/profile geo values.
`viewport`	No	Browser viewport/display size override. Use this to control wide windows, for example { "width": 1366, "height": 768 }.
`sessionKey`	No	Session key for browser context reuse. Defaults to a new unique session; use "default" with userId "cli-default" for the camofox CLI default context. This does not attach to a tab that the CLI already opened.
`timezoneId`	No	IANA timezone override (e.g. "Asia/Tokyo", "Asia/Ho_Chi_Minh")
`geolocation`	No	GPS coordinates override
`proxyProfile`	No	Named proxy profile configured in camofox-browser

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.14.5Jun 22, 2026

changedInput schema / properties / sessionKey / description

Previous value: -"Session key for browser context reuse. Defaults to a new unique session."New value: +"Session key for browser context reuse. Defaults to a new unique session; use \"default\" with userId \"cli-default\" for the camofox CLI default context. This does not attach to a tab that the CLI already opened."

changedInput schema / properties / userId / description

Previous value: -"User ID for session isolation"New value: +"User ID for session isolation. MCP defaults to CAMOFOX_DEFAULT_USER_ID/default; use \"cli-default\" with sessionKey \"default\" to share the camofox CLI default context."

changedInput schema / properties / viewport / description

Previous value: -"Browser viewport size override"New value: +"Browser viewport/display size override. Use this to control wide windows, for example { \"width\": 1366, \"height\": 768 }."

Changed4 schema fields changedv1.14.1May 16, 2026

addedInput schema / properties / geoMode

Added value: +{
+  "description": "Geo merge mode. explicit-wins keeps explicit locale/timezone/geolocation; proxy-locked requires proxy/profile geo values.",
+  "enum": [
+    "explicit-wins",
+    "proxy-locked"
+  ],
+  "type": "string"
+}

addedInput schema / properties / proxy

Added value: +{
+  "description": "Raw proxy override. proxyProfile takes precedence when both are provided.",
+  "properties": {
+    "host": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "password": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "port": {
+      "anyOf": [
+        {
+          "minLength": 1,
+          "type": "string"
+        },
+        {
+          "exclusiveMinimum": 0,
+          "maximum": 9007199254740991,
+          "type": "integer"
+        }
+      ]
+    },
+    "username": {
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "host",
+    "port"
+  ],
+  "type": "object"
+}

addedInput schema / properties / proxyProfile

Added value: +{
+  "description": "Named proxy profile configured in camofox-browser",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / sessionKey

Added value: +{
+  "description": "Session key for browser context reuse. Defaults to a new unique session.",
+  "minLength": 1,
+  "type": "string"
+}

Changed5 schema fields changedv1.6.2May 2, 2026

addedInput schema / properties / geolocation

Added value: +{
+  "description": "GPS coordinates override",
+  "properties": {
+    "latitude": {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    },
+    "longitude": {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude"
+  ],
+  "type": "object"
+}

addedInput schema / properties / locale

Added value: +{
+  "description": "BCP 47 locale override (e.g. \"ja-JP\", \"vi-VN\")",
+  "type": "string"
+}

addedInput schema / properties / preset

Added value: +{
+  "description": "Named geo preset (e.g. \"us-east\", \"us-west\", \"japan\", \"uk\", \"germany\", \"vietnam\", \"singapore\", \"australia\"). Sets locale, timezone, and geolocation.",
+  "type": "string"
+}

addedInput schema / properties / timezoneId

Added value: +{
+  "description": "IANA timezone override (e.g. \"Asia/Tokyo\", \"Asia/Ho_Chi_Minh\")",
+  "type": "string"
+}

addedInput schema / properties / viewport

Added value: +{
+  "description": "Browser viewport size override",
+  "properties": {
+    "height": {
+      "maximum": 2160,
+      "minimum": 240,
+      "type": "integer"
+    },
+    "width": {
+      "maximum": 3840,
+      "minimum": 320,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "width",
+    "height"
+  ],
+  "type": "object"
+}

First observedv1.0.0Feb 13, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that each tab gets a unique fingerprint, and explains the behavior of sharing the CLI context. However, it does not mention what the tool returns, whether it opens a new window, or any potential side effects like rate limits.

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

Conciseness4/5

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

The description is a single paragraph of four sentences, front-loading the core action. It is clear and efficient, though a more structured layout (e.g., bullet points for the CLI sharing case) could improve scannability.

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

Completeness3/5

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

Given 11 parameters including nested objects and no output schema, the description adequately covers the tool's purpose and CLI context behavior. However, it omits return value information and broader tab lifecycle context, leaving some gap for agent decision-making.

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 coverage is 100%, so the baseline is 3. The description adds context for userId/sessionKey sharing and viewport usage, but does not introduce new meaning beyond the schema's detailed descriptions.

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 clearly states 'Create a new browser tab with anti-detection fingerprinting'—a specific verb and resource. It distinguishes from siblings like close_tab and navigate by emphasizing fingerprinting and parameter customization.

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 explicit guidance for sharing the CLI default profile using userId 'cli-default' and sessionKey 'default', and notes that this does not attach to an already open CLI tab. However, it does not explicitly compare to alternatives like load_profile or navigate for creating tabs.

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

create_tab

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools