umbraco-mcp-dev-ops-headless_skill

Overview

This skill guides safe, repeatable developer and operational tasks for headless Umbraco deployments using the MCP tool collections. It focuses on configuration, indexing, webhooks, diagnostics, and models builder workflows to keep delivery APIs reliable. The guidance emphasizes minimal tool usage, validation-first changes, and explicit confirmations for destructive or breaking actions.

How this skill works

The skill inspects Umbraco configuration, document types, data types, search indexes, webhooks, logs, and server health via MCP tool endpoints. For write actions it fetches current scaffolds, validates proposed changes, batches mutations, and reports affected assets. It enforces safety rules like confirmation for deletes and breaking changes, and returns concise summaries and next steps such as rebuilding models or notifying consumers.

When to use it

• Maintain or update headless document types and data types used by APIs
• Rebuild or reconfigure search/indexing for API consumers
• Create or update webhooks to sync downstream systems
• Run health checks and server diagnostics when delivery latency or errors spike
• Validate and deploy Models Builder changes for headless delivery

Best practices

• Request only the minimal tool collections required for the task to limit surface risk
• Always read current configuration and scaffolds before making changes
• Use validation endpoints and preview flows before mutating production assets
• Paginate and batch large operations, showing clear progress and dry-run outputs
• Require explicit confirmation for destructive or API-breaking actions and log permission checks

Example use cases

• Create a new headless Document Type, validate mappings, then trigger Models Builder and report generated models
• Update a Data Type used by clients, run validation, and list impacted API consumers before applying
• Rebuild an external index, track reindex progress, and report item counts and errors
• Add a webhook for Content.Published to sync a downstream search service and verify deliveries
• Run health checks during a spike, collect logs, and produce a prioritized action list for stability