Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

Create Proxy Host

create_proxy_host

Create a proxy host that routes domains to an HTTP or HTTPS upstream without requesting a certificate. Set dry_run=True to preview changes without altering NPM.

Instructions

Create a proxy host that routes the supplied domains to an HTTP or HTTPS upstream. Use this when configuring proxying without requesting a certificate; use create_proxy_host_with_letsencrypt to request one and force HTTPS. NPM stores the host configuration and applies it through its normal config handling. Returns the created host object with its ID, domains, and forwarding settings. Set dry_run=True to preview the exact request without changing NPM.

Input Schema

TableJSON Schema

Name	Required	Description
`dry_run`	No	When True, return the exact request preview without changing NPM.
`ssl_forced`	No	Whether NPM redirects HTTP requests to HTTPS.
`domain_names`	Yes	Domain names routed by this host or certificate.
`forward_host`	Yes	Upstream hostname or IP address.
`forward_port`	Yes	Upstream TCP port number.
`access_list_id`	No	NPM access-list ID to attach; omit for no access list.
`block_exploits`	No	Whether NPM enables its exploit-blocking option.
`certificate_id`	No	NPM certificate ID to attach; omit for no certificate.
`forward_scheme`	Yes	Upstream scheme: http or https.
`caching_enabled`	No	Whether NPM enables proxy caching.
`allow_websocket_upgrade`	No	Whether NPM allows WebSocket upgrades.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.5.2Oct 16, 2026
- addedInput schema / properties / access_list_id / description
```
Added value: +"NPM access-list ID to attach; omit for no access list."
```
- addedInput schema / properties / allow_websocket_upgrade / description
```
Added value: +"Whether NPM allows WebSocket upgrades."
```
- addedInput schema / properties / block_exploits / description
```
Added value: +"Whether NPM enables its exploit-blocking option."
```
- addedInput schema / properties / caching_enabled / description
```
Added value: +"Whether NPM enables proxy caching."
```
- addedInput schema / properties / certificate_id / description
```
Added value: +"NPM certificate ID to attach; omit for no certificate."
```
- addedInput schema / properties / domain_names / description
```
Added value: +"Domain names routed by this host or certificate."
```
- addedInput schema / properties / dry_run / description
```
Added value: +"When True, return the exact request preview without changing NPM."
```
- addedInput schema / properties / forward_host / description
```
Added value: +"Upstream hostname or IP address."
```
- addedInput schema / properties / forward_port / description
```
Added value: +"Upstream TCP port number."
```
- addedInput schema / properties / forward_scheme / description
```
Added value: +"Upstream scheme: http or https."
```
- addedInput schema / properties / ssl_forced / description
```
Added value: +"Whether NPM redirects HTTP requests to HTTPS."
```
First observedv0.5.1Oct 16, 2026

TDQS

A4.5/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 burden; it discloses that NPM persists the host config and applies it through normal config handling, that dry_run returns a preview without changing NPM, and what the response contains. It stops short of permission/auth requirements or reversibility, but the mutation behavior and non-destructive escape hatch are clearly conveyed.

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?

Four sentences, each earning its place: purpose, tool selection, persistence/return behavior, and preview mode. The most decision-relevant routing rule is front-loaded right after the purpose.

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

Completeness5/5

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

For a mutation tool with an output schema present, the agent needs purpose, selection rule, and mutation semantics, and all are supplied. Return values are described even though the output schema already covers them, so nothing required to invoke it correctly is missing.

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 all 11 parameters are already documented in the schema and the baseline is 3. The description only reinforces dry_run behavior and the no-certificate framing, adding little beyond what the schema already says.

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 and resource ('Create a proxy host') plus the routing scope ('routes the supplied domains to an HTTP or HTTPS upstream'). It explicitly names the sibling create_proxy_host_with_letsencrypt as the contrasting option, so an agent can distinguish the two without opening schemas.

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 a direct selection rule: use this when configuring proxying without a certificate, otherwise use create_proxy_host_with_letsencrypt to request one and force HTTPS. It also explains the dry_run preview path, so both the choice-of-tool and the safe-invocation path are covered.

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