Skip to main content
Glama
euisuh

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.
      6
      MIT

    • Caddy MCP

      euisuh
      A
      license
      A
      quality
      C
      maintenance
      MCP server for safely inspecting and operating a local Caddy admin API. Provides read-only tools and dry-run mutations for config management.
      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
      B
      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
      A
      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 30 tools

    Disambiguation5/5

    Each tool targets a distinct resource (proxy host, certificate, access list, redirection host, stream) and action (list, get, create, update, delete, enable, disable, renew). Overlaps are explicitly handled by descriptions, e.g. create_proxy_host vs create_proxy_host_with_letsencrypt and update vs enable/disable. An agent can reliably select the correct tool.

    Naming Consistency5/5

    All tools use a predictable snake_case verb_noun pattern with resource names consistently pluralized for list operations and singular for get/update/delete. Deviations are only necessary qualifiers like with_letsencrypt, which remain readable and consistent. No mixed conventions.

    Tool Count2/5

    At 30 tools, the surface is heavy for the NPM domain. While many operations are distinct, the count exceeds the rubric's 25+ threshold for 'too many' and includes several similar enable/disable variants that could potentially be collapsed.

    Completeness4/5

    The server covers full CRUD and lifecycle for proxy hosts, redirection hosts, streams, and access lists, plus certificate listing, creation, and renewal. Minor gaps include no certificate deletion or single-certificate retrieval, but core workflows are well covered.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources