How to Use the Caddy Server MCP in Claude
Control Caddy Server routing, certificates, and upstreams directly from Claude Desktop without touching a terminal.
Works with every AI agent you already use
…and any MCP-compatible client
Connect Caddy Server MCP to Claude Desktop
Create your Vinkius account to connect Caddy Server to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Live Caddy Server config edits via Claude Desktop
The `load_config` tool lets your agent swap out your active Caddy Server JSON or Caddyfile configuration without restarting the process. This MCP Server runs via local stdio to pipe these changes directly to your running Caddy instance, meaning you can test routing changes instantly inside Claude Desktop. If you want to make surgical updates instead of full rewrites, your Claude Desktop agent can call `replace_config` or `insert_config` to modify specific JSON paths in your Caddy config. You get immediate feedback in the chat window, letting you debug Caddyfile syntax errors before they hit your live Caddy Server.
Inspect upstream health in Claude Desktop
The `get_upstreams` tool exposes the real-time status of your Caddy Server proxy backends directly to Claude Desktop. When a backend service starts failing, your Claude Desktop agent can pull this data to pinpoint which upstream target is offline. Combine this with `get_metrics` to grab Prometheus-formatted performance data from Caddy Server during a debugging session. Your Claude Desktop agent analyzes the raw metrics to explain why requests are piling up or why Caddy is throwing 502 gateway errors.
Manage local PKI certs using this MCP Server
The `get_pki_ca` and `get_pki_ca_certs` tools give your Claude Desktop agent direct access to Caddy Server's internal certificate authority details. This MCP Server lets Claude Desktop inspect your Caddy TLS setup without you having to run shell commands in a separate terminal. If your local Caddy Server site throws SSL warnings, your Claude Desktop agent calls these tools to verify the active certificate chain. You can diagnose local trust issues inside Claude Desktop because the agent sees the exact CA configuration Caddy Server is presenting.
Set up Caddy Server MCP in Claude Web or Desktop
- 1
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
- 2
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcpReplace[YOUR_TOKEN_HERE]with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials. - 3
Start a conversation
Open a new chat. The Caddy Server MCP tools are available immediately — no restart needed.
Endpoint URL
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp No configuration file needed — paste the URL directly in the Claude web interface.
Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about Caddy Server MCP in Claude Desktop
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the Caddy Server MCP today
We host it, we monitor it, we maintain it. You just paste one token.