4,000+ servers built on vurb.ts
Vinkius

Caddy Server MCP Server for VS Code CopilotGive VS Code Copilot instant access to 13 tools to Adapt Config, Append Config, Delete Config, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Caddy Server MCP Server for VS Code Copilot is a standout in the Developer Tools category — giving your AI agent 13 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "caddy-server": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Caddy Server and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
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

About Caddy Server MCP Server

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

GitHub Copilot Agent mode brings Caddy Server data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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.

The Caddy Server MCP Server exposes 13 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 13 Caddy Server tools available for VS Code Copilot

When VS Code Copilot connects to Caddy Server through Vinkius, your AI agent gets direct access to every tool listed below — spanning web-server, reverse-proxy, api-gateway, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

adapt

Adapt config on Caddy Server

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

append

Append config on Caddy Server

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

delete

Delete config on Caddy Server

Deletes the value at the named path in Caddy config

get

Get config on Caddy Server

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

get

Get config by id on Caddy Server

Access a configuration object directly via its @id field

get

Get metrics on Caddy Server

Exposes metrics in Prometheus exposition format

get

Get pki ca on Caddy Server

Returns information about a particular PKI app CA

get

Get pki ca certs on Caddy Server

Returns the certificate chain for a particular CA

get

Get upstreams on Caddy Server

Returns the current status of configured proxy upstreams

insert

Insert config on Caddy Server

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

load

Load config on Caddy Server

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

replace

Replace config on Caddy Server

Strictly replaces an existing object or array element in Caddy config

stop

Stop server on Caddy Server

Gracefully shuts down the Caddy server and exits the process

Connect Caddy Server to VS Code Copilot via MCP

Follow these steps to wire Caddy Server into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Caddy Server

Ask Copilot: "Using Caddy Server, help me...". 13 tools available

Why Use VS Code Copilot with the Caddy Server MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Caddy Server through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Caddy Server + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Caddy Server MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Caddy Server in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Caddy Server immediately.

01

"Get the full JSON configuration of my Caddy server."

02

"Adapt this Caddyfile to JSON: 'example.com { reverse_proxy localhost:8080 }'"

03

"Check the status of my proxy upstreams."

Troubleshooting Caddy Server MCP Server with VS Code Copilot

Common issues when connecting Caddy Server to VS Code Copilot through Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Caddy Server + VS Code Copilot FAQ

Common questions about integrating Caddy Server MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Explore More MCP Servers

View all →