What problem does it solve? It clarifies how the decocms/mcps monorepo deploys MCPs across two platforms (kubernetes-bun and Cloudflare Workers), helping you understand why a deploy or registry publish did or did not trigger and how to onboard a new MCP into the pipeline. ## Core Features & Use Cases - Workflow Mapping: Documents the four GitHub Actions workflows (checks.yml, publish-registry.yml, deploy.yml, publish-jsr.yml), their triggers, and which MCP types each handles. - Detection Logic: Explains how detect-changed-mcps.ts and deploy.json watch patterns determine which MCPs get built, deployed, or published to the registry. - Onboarding Guide: Provides step-by-step instructions for adding custom servers, Cloudflare Worker MCPs, and external app.json-only servers to the pipeline. - Use Case: A new MCP was merged to main but never deployed; use this Skill to determine whether it needs a deploy.json entry, a wrangler.toml, or just an app.json for registry publishing. ## Quick Start Explain why my new MCP in the decocms/mcps repo was not deployed after merging to main and what configuration it needs.
