Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

Create Redirection Host

create_redirection_host

Create an Nginx Proxy Manager host that redirects domains to a destination URL with a chosen HTTP status (301, 302, 307, 308). Use it for URL redirection; preview with dry_run before applying.

Instructions

Create a host that redirects requests for domains to a destination using the selected HTTP status. Use this for URL redirection; use create_proxy_host to forward requests to an upstream server. NPM stores the redirect configuration; an attached certificate ID is referenced without requesting a certificate. Returns the created host object with its ID and redirect settings. Set dry_run=True to preview the exact request without changing NPM.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`preserve_path`	No	Whether to preserve the original request path in the redirect.
`block_exploits`	No	Whether NPM enables its exploit-blocking option.
`certificate_id`	No	NPM certificate ID to attach; omit for no certificate.
`forward_scheme`	No	Scheme of the redirect destination: http or https.	https
`forward_http_code`	No	HTTP redirect status: 301, 302, 307, or 308.
`forward_domain_name`	Yes	Destination hostname or URL for redirected requests.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.5.2Oct 16, 2026

addedInput schema / properties / block_exploits / description

Added value: +"Whether NPM enables its exploit-blocking option."

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_domain_name / description

Added value: +"Destination hostname or URL for redirected requests."

addedInput schema / properties / forward_http_code / description
```
Added value: +"HTTP redirect status: 301, 302, 307, or 308."
```

addedInput schema / properties / forward_scheme / description

Added value: +"Scheme of the redirect destination: http or https."

addedInput schema / properties / preserve_path / description

Added value: +"Whether to preserve the original request path in the redirect."

addedInput schema / properties / ssl_forced / description

Added value: +"Whether NPM redirects HTTP requests to HTTPS."

First observedv0.5.1Oct 16, 2026

TDQS

A3.9/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 burden and does add value — it discloses that no certificate is requested when a certificate_id is referenced, and that dry_run previews without changing NPM. However, it omits permissions/auth requirements, whether the operation is reversible, and side effects of creation, which are material for an un-annotated mutation tool.

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?

Five sentences with the purpose front-loaded ahead of the sibling routing and behavioral notes. Slightly redundant with schema on dry_run, but generally tight and well-ordered.

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 the return-value sentence is supplementary rather than required; the description nonetheless acknowledges the returned host object. For a 9-param mutation tool with no annotations, it is nearly complete, missing only permission/prerequisite context.

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 baseline is 3; the schema documents all nine parameters including defaults and valid HTTP codes. The description reinforces the cert-reference and dry_run semantics but adds little beyond what the schema already provides.

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+resource ('Create a host that redirects requests for domains to a destination') and immediately contrasts with the sibling create_proxy_host. An agent can distinguish it from create_proxy_host and create_stream without opening a schema.

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?

Explicitly routes usage: 'Use this for URL redirection; use create_proxy_host to forward requests to an upstream server.' The condition selecting the alternative is stated clearly. It does not cover the other redirection-host lifecycle siblings, but the core when-to-use vs alternative is fully specified.

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