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

Bring Web Server
to CrewAI

Learn how to connect Caddy Server to CrewAI 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 CrewAI?

When paired with CrewAI, Caddy Server becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Caddy Server tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Caddy Server in CrewAI

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 CrewAI 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 CrewAI

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 CrewAI 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 CrewAI

Every tool call from CrewAI 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 does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →