MCP Tools DirectoryAbout this integration
MCP server for managing Caddy web servers via the admin API
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 2.5.2
- Package
- @yawlabs/caddy-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@yawlabs/caddy-mcpPublisher README and package manifest reviewed. Authentication depends on the target Caddy deployment and can be absent, an optional Bearer token, or Unix-socket filesystem permissions; the package and target server were not executed.
Capabilities: Read and modify Caddy configuration and routes, Inspect TLS, PKI, upstream health, and Prometheus metrics, Save and apply Caddy configuration snapshots
Connected profiles
Additional details
io.github.YawLabs/caddy-mcp
Source ↗ · Checked 2026-09-172.5.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@yawlabs/caddy-mcp
Source ↗ · Checked 2026-09-202.5.3
Source ↗ · Checked 2026-09-20The MCP client launches the local server after configuration; the publisher documents Node.js 20 or newer and Caddy 2.x as requirements.
Source ↗ · Checked 2026-09-20Authentication is deployment-specific: Caddy's local admin API defaults to no token, while protected endpoints may use CADDY_API_TOKEN and Unix sockets rely on filesystem permissions.
Source ↗ · Checked 2026-09-20Launch with npx -y @yawlabs/caddy-mcp@latest; CADDY_ADMIN_URL selects the HTTP, HTTPS, or Unix-socket admin endpoint.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20