Bring Web Server
to VS Code Copilot
Learn how to connect Caddy Server to VS Code Copilot and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 VS Code Copilot?
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.
- —
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
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Caddy Server in VS Code Copilot
Caddy Server and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Caddy Server to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
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.
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.
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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Mapflow
7 toolsExtract geospatial features from satellite imagery with AI that detects buildings, roads, and vegetation patterns automatically.
Enverus Energy Intelligence
10 toolsEquip your AI agent to access global energy data, track drilling rigs, and monitor well production via the Enverus API.
Motion (AI Calendar & Task Management)
10 toolsManage your schedule via Motion — create AI-optimized tasks, track projects, and audit your timeline.
OpenFGA (Fine-Grained Auth)
16 toolsManage fine-grained authorization with OpenFGA — create stores, define authorization models, and manage relationship tuples directly from your AI agent.