nginxpm-mcp
Related Servers
Alternatives to nginxpm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables management of Nginx Proxy Manager instances for configuring proxy hosts, requesting Let's Encrypt SSL certificates, and managing access lists. It allows users to control their web proxy infrastructure through natural language commands in MCP-compatible environments.503MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Nginx Proxy Manager, including proxy hosts, SSL certificates, streams, and more.4 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Nginx Proxy Manager instances through natural language, covering 28 tools for proxy hosts, certificates, streams, and more.MIT
- AlicenseBqualityCmaintenanceEnables AI agents to manage Nginx Proxy Manager (reverse proxies, streams, redirects, and Let's Encrypt certificates) through natural language commands.3023 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables conversational management of Nginx Proxy Manager, including reverse-proxy routing, TLS certificates, access lists, and stream forwards, with built-in safety guardrails for production use.1MIT
- AlicenseCqualityCmaintenanceMCP server that abstracts the Nginx Proxy Manager API, enabling management of proxy hosts, redirections, streams, certificates, access lists, and users through natural language.548 npm1AGPL 3.0
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.