Skip to main content
Glama
euisuh

Nginx Proxy Manager MCP

by euisuh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create Stream

create_stream

Forward raw TCP or UDP traffic from a public port to a destination host and port in Nginx Proxy Manager, with optional dry-run preview.

Instructions

Create a TCP/UDP port forward from an incoming port to a destination host and port. Use this for raw TCP or UDP forwarding; use proxy-host tools for HTTP/HTTPS domain routing. NPM stores the stream configuration and applies it through normal config handling. Returns the created stream object with its ID, ports, and protocol flags. Set dry_run=True to preview the exact request without changing NPM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoWhen True, return the exact request preview without changing NPM.
incoming_portYesPublic TCP/UDP port number accepted by this stream.
tcp_forwardingNoWhether this stream forwards TCP traffic.
udp_forwardingNoWhether this stream forwards UDP traffic.
forwarding_hostYesHostname or IP address receiving stream traffic.
forwarding_portYesDestination TCP/UDP port number.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.2
    • addedInput schema / properties / dry_run / description
      Added value: +"When True, return the exact request preview without changing NPM."
    • addedInput schema / properties / forwarding_host / description
      Added value: +"Hostname or IP address receiving stream traffic."
    • addedInput schema / properties / forwarding_port / description
      Added value: +"Destination TCP/UDP port number."
    • addedInput schema / properties / incoming_port / description
      Added value: +"Public TCP/UDP port number accepted by this stream."
    • addedInput schema / properties / tcp_forwarding / description
      Added value: +"Whether this stream forwards TCP traffic."
    • addedInput schema / properties / udp_forwarding / description
      Added value: +"Whether this stream forwards UDP traffic."
  2. First observedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that NPM stores the configuration and applies it through normal config handling, that it returns the created object with ID/ports/protocol flags, and that dry_run previews without mutating. It omits auth/permission requirements and any restart or propagation behavior, but that is a modest gap for a straightforward create.

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?

Four tight sentences, front-loaded with the core action before the routing alternative and the return/dry-run notes. Slightly redundant in restating the return payload and dry_run behavior that the schema and output schema already convey.

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?

An output schema exists, so explaining the return object is optional, and the create is a single flat mutation with fully documented parameters. What remains thin is permission/prerequisite context, which matters for a create tool with no annotations.

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%, so every parameter is already documented in the input schema, establishing a baseline of 3. The description only echoes dry_run semantics (already in the schema) and refers generically to 'protocol flags' rather than adding new meaning to tcp_forwarding/udp_forwarding defaults.

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?

States a specific verb (Create) plus resource (TCP/UDP port forward) and the exact scope (incoming port to destination host and port). It explicitly distinguishes itself from the sibling proxy-host tools by naming the alternative category for HTTP/HTTPS domain routing.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this for raw TCP or UDP forwarding, use proxy-host tools for HTTP/HTTPS domain routing. It also names the dry_run preview mode as a safe alternative to committing the create, so the agent knows both the routing decision and the pre-flight option.

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