
by YawLabs
An MCP server from Yaw Labs for managing Caddy web servers through Caddy's admin API. It provides 18 tools and 4 resources for config, routes, reverse proxies, TLS, PKI and metrics.
PluginContact for pricing
Step 1: Make sure Caddy's admin API is enabled; it listens on localhost:2019 by default.
Step 2: Add the caddy server to .mcp.json using npx -y @yawlabs/caddy-mcp@latest, with cmd /c on Windows.
Step 3: Set CADDY_ADMIN_URL if Caddy is in Docker or on a remote host.
Step 4: Restart your MCP client and approve the server.
Step 5: Ask for tasks such as listing routes or proxying a hostname to a local port.
To the admin API at CADDY_ADMIN_URL, which defaults to http://localhost:2019. Unix sockets are also supported.
No. CADDY_API_TOKEN is optional and only matters to an authenticating proxy in front of the admin endpoint.
A write to the config root is refused without confirm=true and a snapshot is taken first.
Yes. Set CADDY_ADMIN_URL to the container address, such as http://caddy:2019.
Requirements
CtxLint MCPctxlint checks AI agent context files and MCP server configs against your real codebase and flags drift before your agent acts on it. It runs as a CLI, CI step, pre-commit hook or MCP server.
YawLabs Redis MCPAn MCP server from Yaw Labs for exploring and diagnosing Redis and Valkey instances from an MCP client. It is read-only by default and always enumerates keys with SCAN.
YawLabs AWS MCP@yawlabs/aws-mcp is a small MCP server that calls AWS through your local aws CLI, with built-in SSO re-login, generic resource CRUD and live docs lookup. It is presented as an alternative to AWS's own MCP server.
Docker MCPdocker-mcp-server lets AI agents manage Docker containers, images, networks, volumes, swarm and more through typed MCP tools. It can manage several local or remote daemons in one session.