Skip to main content
Glama
YawLabs

@yawlabs/caddy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @yawlabs/caddy-mcp

No user-submitted related servers found.

    Related Servers

    • Caddy MCP

      euisuh
      A
      license
      A
      quality
      B
      maintenance
      MCP server for safely inspecting and operating a local Caddy admin API. Provides read-only tools and dry-run mutations for config management.
      7
      MIT

    • Coolify MCP Server

      mctlhq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing a self-hosted Coolify PaaS from Claude, Cursor, or any MCP client through 45 tools for deploying, rolling back, debugging, and operating applications, databases, services, projects, and environments in plain English. Destructive operations pause for human confirmation and secrets stay masked.
      9,399 npm
      MIT

    • master-mcp

      Raindancer118
      F
      license
      A
      quality
      B
      maintenance
      Enables unified administrative control over Cloudflare, Porkbun, Docker, Proxmox VE, Nginx Proxy Manager/NPMPlus, Uptime Kuma, Authentik, and Coolify. Exposes service discovery and action execution through three MCP tools with roughly 150 cataloged operations for managing DNS, containers, VMs, proxies, monitors, users, and related infrastructure.
      3
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 18 tools

    Disambiguation4/5

    Multiple tools can write config (caddy_config_set, caddy_config_by_id, caddy_load, caddy_add_route, caddy_reverse_proxy), and delete overlaps similarly (caddy_config_delete vs caddy_remove_route), so boundaries are not perfectly clean. However, the descriptions go to great lengths to explain when each applies (low-level path vs @id vs convenience wrapper), making selection tractable for an agent.

    Naming Consistency4/5

    Every tool carries the caddy_ prefix in consistent snake_case, forming recognizable families (config_get/set/delete, list_servers/routes, add_route/remove_route). Minor deviation: several tools are bare nouns (caddy_status, caddy_metrics, caddy_upstreams, caddy_pki) rather than verb_noun, but the overall pattern is predictable.

    Tool Count4/5

    18 tools is on the heavier side but each earns a place, spanning config CRUD, route helpers, snapshots, TLS/PKI, metrics, and lifecycle. Slightly over what a minimal config server would need, but well-scoped for Caddy's breadth.

    Completeness5/5

    The surface covers the full config lifecycle (read, write, delete, whole-config load, snapshot/revert), route management, TLS/PKI configuration, observability (metrics, upstreams), format adaptation, and graceful shutdown. No obvious dead ends for administering Caddy via its admin API.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources