Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nex_browser_open

Starts NexBrowser environments and returns per-window status. Pass all window IDs in one array for multi-window tasks so Desktop batch-starts and tiles them before automation sessions.

Instructions

Start NexBrowser environments and return per-window status. For multi-window tasks, pass every window ID in one windowId array so Desktop can batch-start and tile them before creating automation sessions.

Input Schema

NameRequiredDescriptionDefault
idsNoAlias of windowId
teamIdYes
windowIdNoOne window ID, or all target window IDs in one array for a single batch-start request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.10.24
    • changedInput schema / properties / ids / description
      Previous value: -"Documented alias of windowId"New value: +"Alias of windowId"
  2. Changed2 schema fields changedv2026.8.20
    • addedInput schema / properties / ids
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    {
+      "items": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "number"
+          }
+        ]
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Documented alias of windowId"
+}
    • changedInput schema / required
      Previous value: -[
-  "teamId",
-  "windowId"
-]New value: +[
+  "teamId"
+]
  3. Addedv2026.8.14

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does reveal two non-obvious traits: it returns per-window status and Desktop tiles windows as part of a batch-start. However, it says nothing about permissions, idempotency for already-running windows, failure modes, or partial-batch outcomes, which matter for a start/mutation operation.

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?

Two sentences, zero filler, with the primary action stated first and the multi-window batching instruction second. Every clause carries actionable information.

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?

For a start/environment-mutation tool with no annotations and no output schema, the description covers what it does and the batching strategy, and it mentions the per-window status return. It omits prerequisites (auth, team scope), behavior when targets are already running, and error semantics, leaving meaningful gaps.

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 67% and the windowId/ids alias is already documented in the schema; the description reinforces why an array is preferred (batch-start and tiling) rather than restating the format. teamId, required but undescribed in the schema, receives no clarification in the description either, so it does not fully compensate for the coverage gap.

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

Purpose4/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 ("Start NexBrowser environments") plus a return behavior ("per-window status"), which an agent can distinguish from lifecycle siblings like nex_browser_create or nex_browser_connect. It stops short of explicitly naming the boundary versus those siblings, so a 4 rather than a 5.

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?

It gives a concrete usage rule: for multi-window tasks, pass every window ID in one windowId array so Desktop can batch-start and tile them, and it implies this happens before creating automation sessions. That is clear procedural context, but it does not state when NOT to use it (e.g. already-running windows) or name an alternative tool.

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

Deploy Server

Other Tools