Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

List Proxy Hosts

list_proxy_hosts

List Nginx Proxy Manager proxy hosts with their status to find host IDs before updating, enabling, disabling, or deleting them. Filter by domain or enabled state without changing NPM.

Instructions

List proxy hosts configured in NPM, including their current status. Use this to find host IDs before get, update, enable, disable, or delete operations. It does not change NPM or request a certificate. Filter domain names by a case-insensitive substring with domain. Filter status with enabled. Set compact=True to return only summary fields. Returns a list of host objects with IDs, domains, forwarding settings, and status.

Input Schema

Name	Required	Description
`domain`	No	Case-insensitive substring to match against any domain name; omit for all domains.
`compact`	No	Return only summary fields when True; defaults to full NPM objects.
`enabled`	No	Keep items with this enabled status; omit for both enabled and disabled items.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.0Oct 18, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return only summary fields when True; defaults to full NPM objects.",
+  "type": "boolean"
+}

addedInput schema / properties / domain

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Case-insensitive substring to match against any domain name; omit for all domains."
+}

addedInput schema / properties / enabled

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Keep items with this enabled status; omit for both enabled and disabled items."
+}

First observedv0.5.1Oct 16, 2026

TDQS

A4.1/5.0

Behavior4/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 well: it asserts read-only behavior ('does not change NPM or request a certificate'), discloses the return shape (list of host objects with IDs, domains, forwarding settings, status), and documents the compact vs full return mode. It omits pagination, ordering, and auth/perm requirements, which keeps it below a 5.

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 core action, then usage, then filters, then return shape – four tight sentences with no filler. The final return-shape sentence is mildly redundant against the existing output schema, but still useful.

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 low-complexity filtered list tool with a full output schema, the description covers purpose, usage, filters, and mutation-safety. Only secondary operational details (ordering, pagination, permissions) are missing, which are not critical here.

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 100%, so the schema already documents all three parameters in equivalent terms (case-insensitive substring, compact summary, enabled filter). The description restates them without adding new syntax or edge-case semantics, so the baseline 3 applies.

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 ('List proxy hosts configured in NPM') plus scope ('including their current status'), which cleanly separates it from get_proxy_host, find_host_by_domain, and create_proxy_host. An agent can identify what it returns and where it fits without opening other tool schemas.

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 names the downstream use case ('find host IDs before get, update, enable, disable, or delete operations') and rules out a class of alternatives with 'It does not change NPM or request a certificate.' It stops short of naming a specific competing listing tool (e.g. find_host_by_domain) as the alternative, so it is clear but not fully routing.

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