caddy-ui
macOS menu bar app for managing local Caddy reverse proxies, with an MCP server
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/michalkvasnicak--caddy-ui)HTML
<a href="/listings/michalkvasnicak--caddy-ui"><img src="/api/listings/michalkvasnicak--caddy-ui/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
With the Xcode command-line tools installed:
brew install caddy make run
After code changes, quit Caddy UI from the menu bar before running `make run` again. Use `make app` to build without opening it.
Use the server icon in the menu bar to start or stop Caddy or open **Manage Targets…**. Enter a name such as `app` and an upstream such as `127.0.0.1:3000`. The editor adds `.localhost:8443` and the list shows the full URL, `https://app.localhost:8443`. Caddy listens on IPv4 loopback only and requires port 8443 to be free. Upstreams still use a hostname or IPv4 address and a port.
After starting Caddy, import `~/Library/Application Support/CaddyUI/tls/pki/authorities/local/root.crt` into your login keychain using Keychain Access and trust it for SSL. This is Caddy UI’s local CA certificate; only the public `root.crt` should be imported, never `root.key`. Caddy UI does not change your trust settings automatically.
Edits are saved immediately and loaded into the running instance. If a reload fails, the saved changes are kept; retry from the targets window or restart Caddy. Quitting the app requests shutdown of its Caddy process. Targets and Caddy logs live in `~/Library/Application Support/CaddyUI/`.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 70 lines
- # Caddy UI
- A macOS 14+ menu bar app for running a dedicated Caddy instance and managing local reverse proxies. It does not modify an existing Caddyfile or control Homebrew services.
- ## Install and open
- With the Xcode command-line tools installed:
- ```sh
- brew install caddy
- make run
- ```
- After code changes, quit Caddy UI from the menu bar before running `make run` again. Use `make app` to build without opening it.
- Use the server icon in the menu bar to start or stop Caddy or open **Manage Targets…**. Enter a name such as `app` and an upstream such as `127.0.0.1:3000`. The editor adds `.localhost:8443` and the list shows the full URL, `https://app.localhost:8443`. Caddy listens on IPv4 loopback only and requires port 8443 to be free. Upstreams still use a hostname or IPv4 address and a port.
- After starting Caddy, import `~/Library/Application Support/CaddyUI/tls/pki/authorities/local/root.crt` into your login keychain using Keychain Access and trust it for SSL. This is Caddy UI’s local CA certificate; only the public `root.crt` should be imported, never `root.key`. Caddy UI does not change your trust settings automatically.
- Edits are saved immediately and loaded into the running instance. If a reload fails, the saved changes are kept; retry from the targets window or restart Caddy. Quitting the app requests shutdown of its Caddy process. Targets and Caddy logs live in `~/Library/Application Support/CaddyUI/`.
- ## Launch at login
- Quit Caddy UI if it’s running, then run `make install` to build and copy it to `/Applications/CaddyUI.app`. Open that copy and choose **Launch at Login** from the menu bar. If macOS asks for approval, open **System Settings → General → Login Items & Extensions** to enable it. To turn it off, choose **Disable Launch at Login** from the menu bar.
- This opens Caddy UI after you sign in; it does not start the Caddy server automatically.
- ## CLI: register a route and print a port
- Keep Caddy UI open and start Caddy from the menu bar. To make the CLI available on your PATH, symlink the executable after building:
- ```sh
- mkdir -p ~/.local/bin
- ln -s "$PWD/.build/CaddyUI.app/Contents/MacOS/CaddyUI" ~/.local/bin/caddy-ui
- ```
- With `~/.local/bin` on your PATH, run this from a project directory:
- ```sh
- port=$(caddy-ui serve) && npm run dev -- --port "$port"
- port=$(caddy-ui serve --name web) && npm --prefix apps/web run dev -- --port "$port"
- ```
- Without `--name`, the CLI uses the current directory name, lowercased with unsupported characters replaced by hyphens. With `--name web`, the URL is `https://web.localhost:8443`. The command adds or updates the target, prints only the allocated port, and exits without starting a server. The target stays registered until you remove it. Run `caddy-ui help` for usage.
- ## Local MCP
- Keep the menu bar app open. In a client that supports stdio MCP servers, point it at the app executable using an absolute path:
- ```json
- {
- "mcpServers": {
- "caddy-ui": {
- "command": "/absolute/path/to/.build/CaddyUI.app/Contents/MacOS/CaddyUI",
- "args": ["--mcp"]
- }
- }
- }
- ```
- The stdio bridge talks to the running app over a Unix socket in its private data directory; no MCP TCP port is opened. Only configure clients you trust to manage the targets and Caddy process.
- | Tool | Arguments |
- | --- | --- |
- | `list_targets` | None; also returns Caddy status and whether a reload is pending |
- | `add_target` | `host` (e.g. `app.localhost`, no port), `upstream` |
- | `edit_target` | `original_host`, `host`, `upstream` |
- | `remove_target` | `host` |
- | `start_caddy` | None |
- | `stop_caddy` | None |
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.