Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_proxy_create

Creates custom proxy resources from protocol, host, and port, or adds several proxies in one call; credentials stay write-only and are never returned.

Instructions

Create one custom proxy resource from protocol, host, and port, or pass items to create several. Prefer nex_proxy_import when the user pasted Desktop-compatible lines. Credentials are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nex_proxy_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoProxy host or IP; required unless items is set
portNoProxy port
itemsNoCreate several proxies in one call; each item needs host and port
remarkNo
passwordNoWrite-only
protocolNoSOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating
usernameNoWrite-only
ipVersionNoIPv4 or IPv6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2026.11.3
    • removedInput schema / properties / items / items / properties / port / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / items / items / properties / port / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / port / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / port / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed6 schema fields changedv2026.10.24
    • changedInput schema / properties / items / items / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / items / items / properties / protocol / description
      Previous value: -"SOCKS5, HTTP, or HTTPS; omitted create defaults to SOCKS5"New value: +"SOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating"
    • changedInput schema / properties / items / items / properties / username / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / protocol / description
      Previous value: -"SOCKS5, HTTP, or HTTPS; omitted create defaults to SOCKS5"New value: +"SOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating"
    • changedInput schema / properties / username / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully states that credentials are never returned, but the schema already marks username and password as 'Write-only', so much of that is redundant. It says nothing about validation, duplicate proxies, failure behavior on partial batch failure, or permissions.

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?

Three short sentences with zero waste: creation mode first, sibling alternative second, credential behavior as a closing caveat. Nothing is buried or repeated.

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?

For a no-annotation, no-output-schema create tool with eight parameters, the description covers the two creation modes, the alternative tool, and credential handling. It could say more about partial-failure semantics for items and what the call returns, but the essentials for correct invocation are present.

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 88%, so the schema already documents host, port, protocol default, ipVersion and write-only credentials. The description only restates that protocol, host and port are the core inputs and that items takes a list; it adds no format or constraint detail beyond the schema.

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 names a specific verb and resource (create a custom proxy) and describes both modes: a single proxy from protocol/host/port, or several via items. It does not distinguish itself from the sibling nex_proxy_batch_create, which appears to overlap heavily with the items path, so the purpose is clear but not fully differentiated.

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 explicitly routes the agent away from this tool when the user pasted Desktop-compatible lines, naming nex_proxy_import as the alternative. It gives no guidance on when to use items versus nex_proxy_batch_create, leaving the most likely sibling confusion unresolved.

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