Caddy MCP Server: Give AI Agents Access to Your Web Server Config and Certificates

Why Give AI Access to Caddy?

Caddy is the modern web server with automatic HTTPS. It handles reverse proxying, load balancing, static file serving, and TLS certificate management with zero configuration. Every site gets HTTPS by default via automatic Let's Encrypt or ZeroSSL certificates.

But when you're coding deployment scripts or debugging routing in Claude or Cursor, your AI assistant can't see your Caddy configuration. It can't check which domains are configured, verify certificate status, or review upstream targets. You keep checking the Caddy admin API or config files manually.

With DataFaucet, you browse your Caddy admin endpoint once and it captures the API calls as MCP tools. Now your AI coding assistant can check routes, certificates, and server config directly.

What AI Agents Can Do With Caddy Access

Once DataFaucet creates an MCP server from your Caddy admin session, AI agents can:

• List configured routes with domains, matchers, and handlers
• Check TLS certificate status with expiry dates and issuers
• View reverse proxy upstreams with health check status
• Monitor active connections and request metrics
• Review server configuration in JSON format
• Check loaded modules and their versions
• View access log patterns and error rates

Setting Up Caddy as an MCP Server with DataFaucet

Step 1: Browse Your Caddy Admin API

Open your Caddy admin API endpoint (default: localhost:2019) or any dashboard you've configured on top of it, and navigate through the config, certificates, and metrics endpoints.

Step 2: DataFaucet Captures the API

DataFaucet's browser extension records the API calls your browser makes to Caddy. Each call becomes a callable MCP tool with parameters and response types.

Step 3: Connect to Your AI Client

Add the generated MCP server to Claude Desktop, Cursor, or Windsurf. Your AI assistant can now query your web server configuration whenever it needs context.

Example: AI Checks Route Config

\\\`

User: What domains is Caddy serving?

AI (via DataFaucet MCP): 6 domains configured:

• api.example.com → reverse_proxy to localhost:8080 (HTTPS, cert valid 82 days)
• app.example.com → reverse_proxy to localhost:3000 (HTTPS, cert valid 79 days)
• docs.example.com → file_server from /var/www/docs (HTTPS, cert valid 85 days)
• grafana.example.com → reverse_proxy to localhost:3001 (HTTPS, cert valid 82 days)
• *.staging.example.com → reverse_proxy to localhost:4000 (wildcard cert, valid 60 days)
• example.com → static_response redirect to app.example.com

\\\`

Example: AI Checks Certificate Health

\\\`

User: Any TLS issues with my Caddy setup?

AI (via DataFaucet MCP): All certificates healthy:

• 6 managed certificates via Let's Encrypt
• Nearest expiry: 60 days (*.staging.example.com)
• Last renewal: 2 days ago (api.example.com)
• OCSP stapling: active on all certs
• No renewal failures in logs

\\\`

Why Not Just Use the Caddy API Directly?

Caddy has an excellent admin API at localhost:2019, but building a dedicated MCP server means writing wrappers for config traversal, handling the nested JSON structure, and maintaining compatibility across Caddy versions.

DataFaucet skips all of that. It watches what your browser does and replicates those exact calls as structured MCP tools. If Caddy updates its config format, you just re-capture.

Works With Any MCP Client

The Caddy MCP server created by DataFaucet works with:

• Claude Desktop and Claude Code
• Cursor (AI-powered editor)
• Windsurf (Codeium's IDE)
• Any MCP-compatible client

Your AI gets real-time data from your Caddy server regardless of which tool you use.

Get Started

Create your Caddy MCP server with DataFaucet — browse your Caddy admin API once, get AI access to your web server config in under two minutes.