nginxpm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NPMCP_CONFIG | Yes | Path to the npm-config.json file containing one or more Nginx Proxy Manager instance configurations. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-proxy-hostsB | List all proxy hosts on an NPM instance. Returns full host details including domains, forwarding config, SSL, and HSTS settings. |
| get-proxy-hostA | Get a single proxy host by ID. Use |
| create-proxy-hostC | Create a new proxy host. Domain names, forward host/port, and scheme are required. SSL, HSTS, caching, and websocket options available. |
| update-proxy-hostC | Update an existing proxy host. Only provided fields are updated. Omit read-only fields (id, created_on, etc.). |
| delete-proxy-hostC | Delete a proxy host by ID. Removes the Nginx vhost configuration. |
| enable-proxy-hostC | Enable a disabled proxy host vhost in Nginx. |
| disable-proxy-hostB | Disable a proxy host vhost in Nginx (returns 502 for matched domains). |
| list-certificatesB | List all certificates on an NPM instance. Includes Let's Encrypt and manual certificates. |
| get-certificateA | Get a single certificate by ID. Use |
| create-certificateB | Create a new certificate. Let's Encrypt is supported for automatic provisioning. Manual provider requires two-step workflow not exposed here. |
| renew-certificateC | Renew a Let's Encrypt certificate. Returns the updated certificate details. |
| delete-certificateB | Delete a certificate by ID. Only certificates not referenced by proxy hosts can be deleted. |
| list-redirection-hostsC | List all redirection hosts on an NPM instance. Redirection hosts forward domains to another URL. |
| get-redirection-hostB | Get a single redirection host by ID. Use |
| create-redirection-hostC | Create a new redirection host. Forwards matched domains to a target URL with configurable HTTP status code. |
| update-redirection-hostC | Update an existing redirection host. Only provided fields are updated. |
| delete-redirection-hostC | Delete a redirection host by ID. |
| enable-redirection-hostC | Enable a disabled redirection host vhost in Nginx. |
| disable-redirection-hostB | Disable a redirection host vhost in Nginx (returns 502 for matched domains). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool pairs a distinct verb with one of three clearly named resources (proxy-host, certificate, redirection-host), so selection is mostly unambiguous. The only soft overlap is enable/disable versus update, since an agent could plausibly toggle a host's state through update-proxy-host instead of the dedicated enable/disable tools.
Every tool follows the same kebab-case verb_noun convention (list-proxy-hosts, get-certificate, create-redirection-host, disable-proxy-host). Resource names are used identically across all verbs, making the naming fully predictable.
19 tools is on the heavier side, but the count is justified: roughly six to seven lifecycle operations each across three resource types (proxy hosts, certificates, redirection hosts). No tool appears redundant or filler.
Proxy hosts and redirection hosts have complete CRUD plus enable/disable, but certificates lack an update operation and the description explicitly notes the manual-provider two-step workflow is not exposed. Broader NPM features (stream/TCP hosts, access lists, dead/404 hosts) are absent, leaving notable gaps for a full Nginx Proxy Manager surface.