Compatible with every major AI agent and IDE
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
- Subscribe to this server
- Enter your Caddy Admin API URL (e.g., http://localhost:2019)
- 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)
Adapts a configuration (e.g., Caddyfile) to JSON without running it
and target is array, expands payload array and appends elements. Sets or replaces an object; appends to an array in Caddy config
Deletes the value at the named path in Caddy config
Leave empty for full config. Exports the configuration at the specified path as JSON
Access a configuration object directly via its @id field
Exposes metrics in Prometheus exposition format
Returns information about a particular PKI app CA
Returns the certificate chain for a particular CA
Returns the current status of configured proxy upstreams
Creates a new object or inserts into an array at a specific index
Use application/json for native JSON, or text/caddyfile for Caddyfile. Sets or replaces the active Caddy configuration
Strictly replaces an existing object or array element in Caddy config
Gracefully shuts down the Caddy server and exits the process
Why Cursor?
Cursor's Agent mode turns Caddy Server into an in-editor superpower. Ask Cursor to generate code using live data from Caddy Server and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Caddy Server in Cursor
Caddy Server and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Caddy Server to Cursor 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Caddy Server in Cursor
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 Cursor 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.

* 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
How Vinkius secures
Caddy Server for Cursor
Every tool call from Cursor to the Caddy Server MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
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.
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Thinkific
10 toolsCreate and sell online courses with a platform that handles course hosting, student enrollment, and payment processing beautifully.

Agendor
6 toolsCRM for sales teams — manage leads, organizations, and pipelines via AI.

Bitly
10 toolsShorten and manage links via Bitly — track clicks, analyze metrics, and manage groups directly from any AI agent.

LinkedIn Ads
6 toolsAccess marketing analytics, campaigns, and reporting via the LinkedIn Ads REST API.
