Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

npm_hosts

Manage Nginx Proxy Manager items such as proxy hosts, redirection hosts, and streams. List, create, update, delete, enable, or disable them via API.

Instructions

List, look at, add, change, delete, enable or disable NPM items.

kind: proxy-hosts, redirection-hosts, dead-hosts, streams, certificates, or access-lists. action: list, get, create, update, delete, enable, disable.

list and get are read only. list gives a short summary unless full=true.
create needs data. Only the main fields are needed. Sensible defaults fill the rest (for proxy-hosts: http, no certificate, block_exploits on). Proxy host example: {"domain_names": ["app.example.com"], "forward_host": "172.16.1.5", "forward_port": 8080, "allow_websocket_upgrade": true}
update needs id and data with ONLY the fields to change. The tool reads the current item and merges, so nothing else is lost.
create, update, enable and disable need confirm=true, after asking the user.
delete needs confirm=true and confirm_phrase='delete '. certificates and access-lists can only be listed, read, or deleted here. To make or change those, use npm_call. Tip: for a new outside address, use its own subdomain as a proxy host. Custom Locations under an existing domain have been unreliable on this NPM.

Input Schema

TableJSON Schema

Name	Required	Default
`id`	No
`data`	No
`full`	No
`kind`	Yes
`action`	No	list
`confirm`	No
`confirm_phrase`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

A4.9/5.0

Behavior5/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: list/get are read-only, list returns a summary unless full=true, create only needs main fields with sensible defaults spelled out, and critically update does a read-merge so untouched fields are preserved. It also discloses the destructive-delete confirmation gate and exact confirm_phrase syntax.

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?

Front-loaded with the action/kind matrix and bulleted per-action rules; nearly every line earns its place. It runs long, and the trailing tip about Custom Locations is opinionated, but it is genuinely actionable rather than filler.

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 7-parameter, multi-action mutation tool with no annotations and 0% schema coverage, the description fills every gap an agent needs: action routing, per-action preconditions, merge semantics, defaults, and confirmation gating. An output schema exists, so return-value detail is rightly omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: kind values, action values, id role, data semantics with a concrete proxy-host example, full=true effect, confirm requirement per action, and confirm_phrase format. All 7 parameters are given meaning beyond the bare JSON types.

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?

The description names the resource (NPM items), enumerates the exact kinds (proxy-hosts, redirection-hosts, dead-hosts, streams, certificates, access-lists) and the full action set, so an agent knows precisely what surface this tool covers. It also explicitly distinguishes itself from sibling npm_call for the certificate/access-list mutation case.

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?

It gives when-to-use routing ('certificates and access-lists can only be listed, read, or deleted here. To make or change those, use npm_call'), preconditions for each action (create needs data, update needs id+data, confirm=true required, delete needs confirm_phrase with exact format), and even a domain tip about subdomains vs Custom Locations.

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

Deploy Server