Skip to main content
Glama
Sign In
Nginx Proxy Manager MCP

Nginx Proxy Manager MCP

by euisuh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Nginx Proxy Manager MCP

No user-submitted related servers found.

    Related Servers

    • swag-mcp

      jmagar
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing SWAG reverse-proxy configurations, including config generation, backups, logs, and health checks. Enables managing nginx subdomain configs for SWAG through a unified action router.
      7
      MIT

    • Nginx Proxy Manager MCP

      VeryBigSad
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      50
      3
      MIT

    • MCP Manager

      daniel3303
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.
      18
      MIT

    • npg-mcp

      four2mis
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for NginxProxyGuard that manages proxy hosts, certificates, SSL, security rules, and nginx configuration through 108+ tools.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes by resource and action, with descriptions that explicitly cross-reference alternatives. However, find_host_by_domain overlaps with domain-filtered list tools, and create_proxy_host vs create_proxy_host_with_letsencrypt could be confused if descriptions are skimmed.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_, get_, create_, update_, delete_, enable_, disable_, find_). The only variation is the descriptive suffix in create_proxy_host_with_letsencrypt, which is still readable and consistent.

    Tool Count3/5

    32 tools is on the heavy side for the domain, though NPM manages several distinct resource types (proxy hosts, redirection hosts, streams, certificates, access lists). Some consolidation is possible (e.g., enable/disable could be status updates via update tools, and letsencrypt creation could be an option on create_proxy_host).

    Completeness4/5

    The surface covers full CRUD and lifecycle (create, get, list, update, delete, enable, disable) for proxy hosts, redirection hosts, streams, and access lists, plus certificate listing and creation. Gaps include certificate deletion (delete_certificate) and custom certificate import, and there is no get_certificate by ID (though listing may suffice).

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources