Skip to main content
Glama
kognar-ai

@kognar/nginx-manager-mcp-server

by kognar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @kognar/nginx-manager-mcp-server

No user-submitted related servers found.

    Related Servers

    • Nginx Proxy Manager MCP

      euisuh
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Nginx Proxy Manager: manage proxy hosts, redirections, streams, Let's Encrypt certificates, and access lists, with dry-run previews on every change and a one-shot HTTPS host workflow.
      32
      49 PyPI
      1
      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

    • 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

    • 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

    C2.7/5.0

    Scored across 54 tools

    Disambiguation5/5

    Each tool has a unique combination of action and resource (e.g., npm_create_proxy_host vs npm_delete_proxy_host). Actions like create, delete, get, list, update, enable, disable are clearly distinct across resource types (proxy_host, redirection_host, stream, etc.), leaving no ambiguity for an agent.

    Naming Consistency5/5

    All tools follow a consistent 'npm_<verb>_<noun>' pattern. Verbs are standard CRUD plus enable/disable, and nouns are resource names. No mixing of camelCase or snake_case, and the pattern is predictable across all 54 tools.

    Tool Count2/5

    With 54 tools, this server has a very high tool count for a single domain. While each tool serves a distinct purpose, the number exceeds the 25+ threshold for 'too many', potentially overwhelming an agent or requiring excessive navigation.

    Completeness5/5

    The tool set covers full CRUD for all major Nginx Proxy Manager resources (proxy hosts, redirection hosts, streams, certificates, access lists, users, settings) plus enabling/disabling, certificate testing and renewal, audit log, and reports. No obvious gaps exist for core proxy management tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources