4,000+ servers built on vurb.ts
Vinkius
Claude CodeCLI
Caddy Server MCP Server

Bring Web Server
to Claude Code

Learn how to connect Caddy Server to Claude Code and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Adapt ConfigAppend ConfigDelete ConfigGet ConfigGet Config By IdGet MetricsGet Pki CaGet Pki Ca CertsGet UpstreamsInsert ConfigLoad ConfigReplace ConfigStop Server

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Caddy Server

What is the Caddy Server MCP Server?

Connect your Caddy Server instance to any AI agent and automate your web infrastructure management through natural conversation.

What you can do

  • Configuration Management — Load, get, append, or replace server configurations using JSON or Caddyfile formats.
  • Caddyfile Adaptation — Instantly convert Caddyfile text into native Caddy JSON without applying the changes.
  • Upstream Monitoring — Check the real-time status and health of your proxy upstreams and backends.
  • PKI & Certificates — Inspect internal CA information and retrieve certificate chains for your managed domains.
  • Metrics & Observability — Access Prometheus-style metrics to monitor server performance and request traffic.
  • Granular Control — Delete specific configuration paths or gracefully stop the server process.

How it works

  1. Subscribe to this server
  2. Enter your Caddy Admin API URL (e.g., http://localhost:2019)
  3. Start managing your reverse proxies and web servers from Claude, Cursor, or any MCP client

Who is this for?

  • DevOps Engineers — automate infrastructure updates and monitor backend health without leaving the terminal or chat.
  • Web Developers — quickly test and adapt Caddyfile configurations during local development.
  • SREs — retrieve live metrics and PKI status to ensure site reliability and security compliance.

Built-in capabilities (13)

adapt_config

Adapts a configuration (e.g., Caddyfile) to JSON without running it

append_config

and target is array, expands payload array and appends elements. Sets or replaces an object; appends to an array in Caddy config

delete_config

Deletes the value at the named path in Caddy config

get_config

Leave empty for full config. Exports the configuration at the specified path as JSON

get_config_by_id

Access a configuration object directly via its @id field

get_metrics

Exposes metrics in Prometheus exposition format

get_pki_ca

Returns information about a particular PKI app CA

get_pki_ca_certs

Returns the certificate chain for a particular CA

get_upstreams

Returns the current status of configured proxy upstreams

insert_config

Creates a new object or inserts into an array at a specific index

load_config

Use application/json for native JSON, or text/caddyfile for Caddyfile. Sets or replaces the active Caddy configuration

replace_config

Strictly replaces an existing object or array element in Caddy config

stop_server

Gracefully shuts down the Caddy server and exits the process

Why Claude Code?

Claude Code registers Caddy Server as an MCP server in a single terminal command. Once connected, Claude Code discovers all 13 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Caddy Server data drives decisions without human intervention.

  • Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart

  • Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

  • Claude Code runs headlessly, enabling unattended batch processing using Caddy Server tools in cron jobs or deployment scripts

  • Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Caddy Server in Claude Code

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Caddy Server and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Caddy Server to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Caddy Server in Claude Code

The Caddy Server MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Caddy Server
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Caddy Server for Claude Code

Every tool call from Claude Code to the Caddy Server MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I use a Caddyfile instead of JSON to update my configuration?

Yes! Use the load_config tool and set the content_type to text/caddyfile. You can also use adapt_config to preview the JSON conversion before applying it.

02

How can I monitor the health of my load-balanced backends?

Use the get_upstreams tool. It returns the current status and health metrics of all configured proxy upstreams in your Caddy instance.

03

Is it possible to remove a specific site or route without resetting the whole server?

Absolutely. Use delete_config with the specific path (e.g., apps/http/servers/srv0/routes/1) to remove only that element from the active configuration.

04

How do I add an MCP server to Claude Code?

Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.

05

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

06

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

07

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

08

Connection timeout

Check your internet connection and verify the Edge URL is reachable

Explore More MCP Servers

View all →