Skip to main content
hc
Submit
mcpSource-backed
Nginx UI logo

Nginx UI MCP Module

Built-in MCP interface for Nginx UI that lets Claude-compatible agents manage Nginx configuration files, inspect Nginx status, reload Nginx, and restart the Nginx service through an authenticated SSE endpoint.

by Nginx UI · submitted by oktofeesh1·added 2026-06-06·11,324 source repo stars·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/nginx-ui-mcp-module
Source URLs
https://raw.githubusercontent.com/0xJacky/nginx-ui/main/docs/guide/mcp.md, https://github.com/0xJacky/nginx-ui
Brand
Nginx UI
Brand domain
nginxui.com
Brand asset source
brandfetch
Safety notes
Nginx UI MCP exposes executable tools for listing, reading, creating, modifying, renaming, enabling, and organizing Nginx configuration files., Service tools can inspect status, reload Nginx, and restart the Nginx service, which can interrupt traffic or apply broken configuration., The MCP endpoint is authenticated through a `node_secret` query parameter; treat it as a secret and rotate it if exposed., Require human review, syntax validation, backups, and deployment windows before enabling configs, reloading, or restarting production Nginx., Limit MCP access to trusted networks and approved clients; do not expose the endpoint publicly without strong transport security and access controls.
Privacy notes
Nginx configuration files can reveal domains, upstream services, internal IPs, ports, TLS paths, certificate references, proxy headers, auth settings, rewrite rules, and deployment topology., MCP requests, responses, logs, screenshots, and chat transcripts can retain configuration contents, node secrets, hostnames, service status, and change history., Restart and reload operations can create operational logs that identify users, timestamps, affected sites, and infrastructure state., Redact `node_secret`, private domains, internal addresses, certificate paths, and customer routing details before sharing prompts or PR notes.
Author
Nginx UI
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

20 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

2 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime1Network & hosting1Review & approval1General220 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes.

5 areas
  • SafetyLocal filesNginx UI MCP exposes executable tools for listing, reading, creating, modifying, renaming, enabling, and organizing Nginx configuration files.
  • SafetyGeneralService tools can inspect status, reload Nginx, and restart the Nginx service, which can interrupt traffic or apply broken configuration.
  • SafetyCredentials & tokensThe MCP endpoint is authenticated through a `node_secret` query parameter; treat it as a secret and rotate it if exposed.
  • SafetyGeneralRequire human review, syntax validation, backups, and deployment windows before enabling configs, reloading, or restarting production Nginx.
  • SafetyPermissions & scopesLimit MCP access to trusted networks and approved clients; do not expose the endpoint publicly without strong transport security and access controls.
  • PrivacyLocal filesNginx configuration files can reveal domains, upstream services, internal IPs, ports, TLS paths, certificate references, proxy headers, auth settings, rewrite rules, and deployment topology.
  • PrivacyCredentials & tokensMCP requests, responses, logs, screenshots, and chat transcripts can retain configuration contents, node secrets, hostnames, service status, and change history.
  • PrivacyData retentionRestart and reload operations can create operational logs that identify users, timestamps, affected sites, and infrastructure state.
  • PrivacyCredentials & tokensRedact `node_secret`, private domains, internal addresses, certificate paths, and customer routing details before sharing prompts or PR notes.

Disclosure: AGPL-3.0-licensed Nginx UI project with a built-in MCP module. Use it only on Nginx deployments where AI-assisted configuration management and service control are explicitly approved.

Safety notes

  • Nginx UI MCP exposes executable tools for listing, reading, creating, modifying, renaming, enabling, and organizing Nginx configuration files.
  • Service tools can inspect status, reload Nginx, and restart the Nginx service, which can interrupt traffic or apply broken configuration.
  • The MCP endpoint is authenticated through a `node_secret` query parameter; treat it as a secret and rotate it if exposed.
  • Require human review, syntax validation, backups, and deployment windows before enabling configs, reloading, or restarting production Nginx.
  • Limit MCP access to trusted networks and approved clients; do not expose the endpoint publicly without strong transport security and access controls.

Privacy notes

  • Nginx configuration files can reveal domains, upstream services, internal IPs, ports, TLS paths, certificate references, proxy headers, auth settings, rewrite rules, and deployment topology.
  • MCP requests, responses, logs, screenshots, and chat transcripts can retain configuration contents, node secrets, hostnames, service status, and change history.
  • Restart and reload operations can create operational logs that identify users, timestamps, affected sites, and infrastructure state.
  • Redact `node_secret`, private domains, internal addresses, certificate paths, and customer routing details before sharing prompts or PR notes.

Prerequisites

  • Running Nginx UI deployment with the MCP module available.
  • MCP client support for SSE or URL-based remote MCP server configuration.
  • Valid `node_secret` for the target Nginx UI node.
  • Review of which Nginx configuration base path, virtual hosts, enabled sites, and service controls the agent may access.
  • Change-management policy for AI-assisted Nginx edits, reloads, restarts, and production traffic impact.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Stars
11,324 source repo stars
Forks
846
Updated
2026-07-20T07:58:16Z
Collection metadata
Estimated setup
20 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
AGPL-3.0-licensed Nginx UI project with a built-in MCP module. Use it only on Nginx deployments where AI-assisted configuration management and service control are explicitly approved.
Full copyable content
{
  "mcpServers": {
    "nginx-ui": {
      "url": "https://<nginx-ui-host>/mcp?node_secret=<node-secret>"
    }
  }
}

About this resource

Content

Nginx UI MCP Module is the built-in Model Context Protocol interface provided by Nginx UI. It exposes an authenticated /mcp endpoint so Claude-compatible agents can manage Nginx configuration files, inspect Nginx status, reload Nginx, and restart the Nginx service through Nginx UI.

Use it when an operations team wants an MCP interface for Nginx configuration management with explicit review around every write, enable, reload, or restart operation.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, MCP overview, README, license, configuration-management guide, Nginx service guide, router source, tool registration source, config modification source, and restart tool source for current setup and behavior details.

Features

  • Provide an authenticated MCP endpoint at the Nginx UI /mcp path.
  • Authenticate MCP access with the node_secret query parameter.
  • List, read, create, modify, rename, and organize Nginx configuration files.
  • Create configuration directories and inspect configuration history.
  • Enable previously created Nginx configurations.
  • Query Nginx status.
  • Reload Nginx configuration.
  • Restart the Nginx service.

Installation

Deploy Nginx UI and identify the target node secret for the Nginx UI instance you want Claude to access. Then configure an MCP client with the authenticated MCP endpoint for that deployment:

{
  "mcpServers": {
    "nginx-ui": {
      "url": "https://<nginx-ui-host>/mcp?node_secret=<node-secret>"
    }
  }
}

Use the actual scheme, host, path, and secret from the approved Nginx UI deployment. Store node_secret in a secret manager or local MCP config that is not committed to a repository.

Use Cases

  • Ask Claude to inspect available Nginx configuration files before proposing a change.
  • Review a virtual host configuration and identify syntax or routing concerns.
  • Draft a config update, then apply it only after human approval.
  • Enable a staged site configuration with explicit confirmation.
  • Check Nginx status during an incident response workflow.
  • Reload Nginx after a reviewed configuration change.
  • Restart Nginx during a planned maintenance window.

Safety and Privacy

Nginx UI MCP Module can change live web-server behavior. Treat every write, enable, reload, and restart operation as production-impacting unless you know the target node is a sandbox. Require human approval, config validation, backups, and a rollback plan before using the write or service-control tools.

Treat node_secret, Nginx configuration contents, hostnames, internal upstreams, TLS paths, status output, change history, logs, and MCP transcripts as sensitive. Limit endpoint exposure to trusted networks and redact operational details before sharing prompts, screenshots, or validation notes.

Duplicate Check

No 0xJacky/nginx-ui, Nginx UI MCP, Nginx UI MCP Module, Nginx configuration MCP, or matching source URL entry was found in content/mcp or README.md. Existing web-server, DevOps, and browser automation entries do not cover Nginx UI's built-in MCP endpoint for Nginx configuration and service management.

#nginx#devops#configuration#server-management#sse

Source citations

Add this badge to your README

Show that Nginx UI MCP Module is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/nginx-ui-mcp-module.svg)](https://heyclau.de/entry/mcp/nginx-ui-mcp-module)

How it compares

Nginx UI MCP Module side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
Nginx UI logoNginx UI MCP Module

Built-in MCP interface for Nginx UI that lets Claude-compatible agents manage Nginx configuration files, inspect Nginx status, reload Nginx, and restart the Nginx service through an authenticated SSE endpoint.

Open dossier
Coolify MCP Server logoCoolify MCP Server

MCP server for Coolify infrastructure management, diagnostics, deployments, logs, projects, environments, applications, databases, services, env vars, storage, scheduled tasks, private keys, cloud tokens, teams, and docs search.

Open dossier
gcloud MCP Server logogcloud MCP Server

Google Cloud gcloud MCP server from googleapis that lets Claude run approved gcloud CLI commands with allowlist and denylist controls for cloud resource inspection, automation, and operations.

Open dossier
MCP Installer Server

MCP server that lets Claude install other MCP servers into Claude Desktop by writing MCP config entries for npm packages, uvx packages, or locally cloned Node-based MCP server projects.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandNginx UI logoNginx UICoolify MCP Server logoCoolify MCP Servergcloud MCP Server logogcloud MCP Server—
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorNginx UIStuart MasonGoogle APIsAnais Betts
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo11.3k repo stars———
Safety notes✓Nginx UI MCP exposes executable tools for listing, reading, creating, modifying, renaming, enabling, and organizing Nginx configuration files. Service tools can inspect status, reload Nginx, and restart the Nginx service, which can interrupt traffic or apply broken configuration. The MCP endpoint is authenticated through a `node_secret` query parameter; treat it as a secret and rotate it if exposed. Require human review, syntax validation, backups, and deployment windows before enabling configs, reloading, or restarting production Nginx. Limit MCP access to trusted networks and approved clients; do not expose the endpoint publicly without strong transport security and access controls.✓Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions. Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once. Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation. Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually. Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure.✓gcloud MCP Server executes gcloud CLI commands with the permissions of the active gcloud account. Allowed commands can create, update, delete, deploy, scale, list, export, or configure Google Cloud resources depending on IAM permissions and selected services. The server blocks command substitution, pipes, redirection, SSH-style commands, interactive commands, and a default set of sensitive command prefixes, but allowed gcloud commands can still have real infrastructure, billing, IAM, and data impact. Use allowlists for narrow workflows and service account impersonation with limited roles when possible. Require human approval for IAM, billing, networking, firewall, storage, database, secret, deployment, delete, and production-impacting commands.✓MCP Installer can write or update Claude Desktop MCP server configuration entries. The install_repo_mcp_server tool can add npx or uvx based MCP server commands from package names the model supplies. The install_local_mcp_server tool can run npm install in a local project with a package.json and configure Node to execute discovered package bins or main files. Environment variables passed to the installer are written into the MCP configuration for the installed server. Treat this as an administrative helper; review every package, version, local path, arg, and environment value before approving a tool call.
Privacy notes✓Nginx configuration files can reveal domains, upstream services, internal IPs, ports, TLS paths, certificate references, proxy headers, auth settings, rewrite rules, and deployment topology. MCP requests, responses, logs, screenshots, and chat transcripts can retain configuration contents, node secrets, hostnames, service status, and change history. Restart and reload operations can create operational logs that identify users, timestamps, affected sites, and infrastructure state. Redact `node_secret`, private domains, internal addresses, certificate paths, and customer routing details before sharing prompts or PR notes.✓Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client. Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors. Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials. Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance. Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs.✓gcloud output can reveal project IDs, resource names, regions, IAM bindings, service accounts, logs, errors, labels, metadata, URLs, secrets references, billing context, and infrastructure topology. Authentication state, ADC files, service account impersonation details, access tokens, project IDs, and local gcloud configuration should stay out of prompts and repository files. Command output may be retained by the MCP client, model provider, terminal logs, shell history, and chat transcripts. Avoid broad listing or export commands against production projects unless data handling and retention have been reviewed.✓MCP configuration files can contain API keys, tokens, local paths, package names, arguments, and environment variables. The server reads and writes the user's Claude Desktop MCP config and may reveal existing MCP server names or config structure through tool results or logs. Local project paths can reveal usernames, repository names, client names, or private workspace layout. Do not ask the installer to write real secrets until you understand where the MCP client stores them and who can read the config file.
Prerequisites
  • Running Nginx UI deployment with the MCP module available.
  • MCP client support for SSE or URL-based remote MCP server configuration.
  • Valid `node_secret` for the target Nginx UI node.
  • Review of which Nginx configuration base path, virtual hosts, enabled sites, and service controls the agent may access.
  • Running Coolify instance with API access enabled.
  • Coolify API access token scoped to the resources Claude may inspect or manage.
  • Node.js 20 or newer for the published npm server.
  • Review of which servers, projects, applications, databases, services, deployments, env vars, private keys, teams, cloud tokens, and scheduled tasks the token can access.
  • Node.js 20 or newer with npm or another compatible package runner.
  • Google Cloud CLI installed and authenticated.
  • Active gcloud account, project, and configuration scoped to the intended environment.
  • Least-privilege user or service account impersonation for the allowed cloud actions.
  • Claude Desktop or another MCP client that can run stdio Node MCP servers.
  • Node.js and npx available for npm-hosted MCP servers.
  • uvx available before installing Python MCP servers through the uvx path.
  • Package names, local paths, args, and environment variables reviewed before asking Claude to install anything.
Install
Install Nginx UI, then connect an MCP client to the authenticated /mcp endpoint with a node_secret.
npx -y @masonator/coolify-mcp
npx -y @google-cloud/gcloud-mcp
Run `npx @anaisbetts/mcp-installer` from Claude Desktop after reviewing the server source and package behavior.
Config
Manual-only setup:
Use the Nginx UI /mcp endpoint with the node_secret query parameter from the target Nginx UI node.
{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "@masonator/coolify-mcp"
      ],
      "env": {
        "COOLIFY_BASE_URL": "https://your-coolify-instance.example",
        "COOLIFY_ACCESS_TOKEN": "your-api-token"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "gcloud": {
      "command": "npx",
      "args": [
        "-y",
        "@google-cloud/gcloud-mcp"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "mcp-installer": {
      "command": "npx",
      "args": ["@anaisbetts/mcp-installer"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Agent Skills in Claude Agent SDK Applications

Use Agent Skills in the Claude Agent SDK: filesystem discovery via settingSources, the skills option to enable or filter, and tool access.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by YB0y

Choosing MCP Transport: Stdio, HTTP, SSE, and WebSocket

Choose MCP stdio, HTTP, SSE, or WebSocket for your deployment.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.