Skip to content
Back to search

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/michalkvasnicak--caddy-ui/badge.svg)](/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

i

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
  1. # Caddy UI
  2. 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.
  3. ## Install and open
  4. With the Xcode command-line tools installed:
  5. ```sh
  6. brew install caddy
  7. make run
  8. ```
  9. After code changes, quit Caddy UI from the menu bar before running `make run` again. Use `make app` to build without opening it.
  10. 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.
  11. 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.
  12. 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/`.
  13. ## Launch at login
  14. 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.
  15. This opens Caddy UI after you sign in; it does not start the Caddy server automatically.
  16. ## CLI: register a route and print a port
  17. Keep Caddy UI open and start Caddy from the menu bar. To make the CLI available on your PATH, symlink the executable after building:
  18. ```sh
  19. mkdir -p ~/.local/bin
  20. ln -s "$PWD/.build/CaddyUI.app/Contents/MacOS/CaddyUI" ~/.local/bin/caddy-ui
  21. ```
  22. With `~/.local/bin` on your PATH, run this from a project directory:
  23. ```sh
  24. port=$(caddy-ui serve) && npm run dev -- --port "$port"
  25. port=$(caddy-ui serve --name web) && npm --prefix apps/web run dev -- --port "$port"
  26. ```
  27. 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.
  28. ## Local MCP
  29. Keep the menu bar app open. In a client that supports stdio MCP servers, point it at the app executable using an absolute path:
  30. ```json
  31. {
  32. "mcpServers": {
  33. "caddy-ui": {
  34. "command": "/absolute/path/to/.build/CaddyUI.app/Contents/MacOS/CaddyUI",
  35. "args": ["--mcp"]
  36. }
  37. }
  38. }
  39. ```
  40. 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.
  41. | Tool | Arguments |
  42. | --- | --- |
  43. | `list_targets` | None; also returns Caddy status and whether a reload is pending |
  44. | `add_target` | `host` (e.g. `app.localhost`, no port), `upstream` |
  45. | `edit_target` | `original_host`, `host`, `upstream` |
  46. | `remove_target` | `host` |
  47. | `start_caddy` | None |
  48. | `stop_caddy` | None |

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.