Skip to main content
Glama
julcap

nginx-certbot-mcp

by julcap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nginx-certbot-mcp

No user-submitted related servers found.

    Related Servers

    • npm-mcp

      omichelbraga
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT

    • npm-mcp

      wadew
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Nginx Proxy Manager instances through natural language, covering 28 tools for proxy hosts, certificates, streams, and more.
      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

    • vps-ops-mcp

      Akdag94
      A
      license
      A
      quality
      A
      maintenance
      A safe, structured MCP server that lets AI inspect and operate a VPS through typed, allowlisted tools for nginx, PM2, SSL, UFW, fail2ban, with read-only defaults and opt-in mutations.
      6
      6 npm
      2
      MIT
    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.4/5.0

    Scored across 23 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: nginx site inspection vs. mutation, cert issuance vs. renewal vs. revocation, and DNS record types are cleanly separated. Cross-references like check_dns vs. check_upstream_health and create_domain_record vs. create_txt_record eliminate ambiguity.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern with predictable verbs: list, get, check, create, delete, update, restore, reload, issue, renew, revoke. There are no mixed conventions or vague generic names.

    Tool Count3/5

    At 23 tools, this is on the heavy end of the scale, though the count is justified by spanning three related areas: nginx site lifecycle, certbot certificate lifecycle, and Route 53 DNS record management. Each tool has a real purpose, but the overall surface area feels larger than a typical focused server.

    Completeness4/5

    The tool surface covers the full lifecycle for nginx sites, certificates, and DNS records: create/read/update/delete/restore for sites, issue/renew/revoke/delete for certs, and upsert/delete for records. Minor gaps exist, such as update_site only rewriting proxy_pass directives rather than supporting arbitrary config edits, but most workflows can be completed without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources