Can I use Caddy as a CLI?

Yes. KosmoKrator exposes a Caddy CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Caddy through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Caddy tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Caddy credentials stored?

Caddy credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Caddy MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Caddy MCP Integration for Generic MCP Clients

Connect Caddy to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 5 read 2 write Bearer token auth

Submit Caddy feedback View package source

Connect Caddy to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Caddy MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-caddy": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=caddy",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=caddy --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Caddy instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Caddy Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Caddy integration catalog.

MCP tool	Source function	Type	Description
`integration__caddy__caddy_list_sites`	`caddy.caddy_list_sites`	Read	List all Caddy sites. Returns site IDs, domain names, status, and configuration details.
`integration__caddy__caddy_get_site`	`caddy.caddy_get_site`	Read	Get detailed information about a specific Caddy site, including its configuration, domain, and status.
`integration__caddy__caddy_create_site`	`caddy.caddy_create_site`	Write	Create a new site in Caddy. Specify the domain name and optional configuration parameters.
`integration__caddy__caddy_delete_site`	`caddy.caddy_delete_site`	Write	Delete a site from Caddy. This action is irreversible and will remove the site and its configuration.
`integration__caddy__caddy_list_certificates`	`caddy.caddy_list_certificates`	Read	List all TLS certificates managed by Caddy. Returns certificate IDs, domains, expiry dates, and status.
`integration__caddy__caddy_get_certificate`	`caddy.caddy_get_certificate`	Read	Get detailed information about a specific TLS certificate, including domain, issuer, validity, and SANs.
`integration__caddy__caddy_get_current_user`	`caddy.caddy_get_current_user`	Read	Get details of the currently authenticated Caddy user. Returns user ID, email, username, and account info.

Related Caddy Pages

Caddy CLIUse direct JSON commands instead of MCP discovery. Caddy MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.