How to Use the Caddy Server MCP in Cursor

Q: How do I validate my Caddyfile syntax using Caddy Server and Cursor?

Your agent runs adaptconfig on your workspace Caddyfile to convert it to JSON. If Caddy Server returns a parser error, Cursor highlights the exact line in your editor so you can fix it instantly.

Q: Can Cursor modify running Caddy Server routing rules?

Yes, Cursor uses replaceconfig to target specific JSON paths in your active Caddy Server configuration. The agent can append new routes or delete old ones on the fly while you write code.

Q: What happens if I need to completely wipe the active configuration?

Your agent can call deleteconfig on any path, or use loadconfig with an empty JSON object to reset the state. This is highly useful for cleaning up temp routes during local testing.

Inject live Caddy Server metrics and configurations directly into your Cursor agent mode sessions via this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Caddy Server MCP to Cursor

Create your Vinkius account to connect Caddy Server to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Caddy Server with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Edit live JSON configs directly from Cursor

The `replace_config` tool allows your Cursor agent to modify active routing blocks inside Caddy Server without breaking your editor flow. By connecting this MCP Server, the editor can patch your active Caddy Server configuration using specific JSON paths. If you need to add a new route, the Cursor agent uses `insert_config` or `append_config` to update your running Caddy instance. You don't have to copy-paste JSON payloads or run terminal commands to apply your Cursor workspace changes to Caddy Server.

Validate Caddyfiles in Cursor with this MCP Server

The `adapt_config` tool converts Caddyfile syntax to JSON formats that your running Caddy Server understands. This MCP Server gives your Cursor agent the ability to check your workspace Caddyfile edits for syntax errors before they go live on your server. If the syntax is valid, the Cursor agent can call `load_config` to push the update directly to Caddy Server. This loop ensures you never break your local Caddy Server with a malformed configuration file written in Cursor.

Debug active proxy upstreams in Cursor

The `get_upstreams` tool pulls the health and load status of your Caddy Server backend proxies directly into your Cursor chat. When your workspace code fails to connect to a microservice, the Cursor agent checks this data to see if Caddy is routing traffic correctly. By combining this with `get_config_by_id`, your Cursor agent can pinpoint which exact upstream block in your Caddy Server JSON configuration is misconfigured. You get immediate, actionable fixes written directly into your Cursor workspace files to correct Caddy's behavior.

Setup guide

Set up Caddy Server MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Caddy Server MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Caddy Server transactions." If the MCP tools are loaded correctly, Cursor will call the Caddy Server tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "caddy-server-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Caddy Server. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Caddy Server now

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 Cursor

Your agent runs `adapt_config` on your workspace Caddyfile to convert it to JSON. If Caddy Server returns a parser error, Cursor highlights the exact line in your editor so you can fix it instantly.

Yes, Cursor uses `replace_config` to target specific JSON paths in your active Caddy Server configuration. The agent can append new routes or delete old ones on the fly while you write code.

You ask the Cursor agent to check your proxy status, and it calls `get_upstreams` to fetch live backend metrics. The agent then displays which Caddy Server targets are responding and which ones are down.

Your agent can call `delete_config` on any path, or use `load_config` with an empty JSON object to reset the state. This is highly useful for cleaning up temp routes during local testing.

All Caddy configuration JSON, PKI certificates, and Prometheus metrics are processed locally inside Cursor's isolated runtime. This MCP Server runs locally, meaning no configuration data or certificate chains are sent to external LLM providers or cloud databases.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript