build-tools

Build Tools

Generate MCP tool collections from the API groups selected during discovery. This skill reads .discover.json and the swagger spec, then builds tool files one collection at a time.

IMPORTANT: This skill ONLY creates tool files, collection indexes, and registrations. Do NOT create any test files, test setup, test builders, test helpers, or __tests__/ directories. Testing is handled separately by the /build-tools-tests skill.

Prerequisites

Before running, ensure:

1. You have run npx @umbraco-cms/create-umbraco-mcp-server discover (.discover.json exists)
2. The API client has been generated (src/umbraco-api/api/generated/ directory exists — if not, run npm run generate)

Arguments

• No arguments: build all collections from .discover.json
• Single collection name: build only that collection (e.g. /build-tools form)

Agents

This skill orchestrates the following agents — use them for the relevant steps:

Agent	When to use
mcp-tool-creator	Creating each tool file (Step 3b)
mcp-tool-description-writer	Writing tool descriptions (Step 3b)
mcp-tool-reviewer	Reviewing tools for LLM-readiness (Step 4)

Workflow

Process one collection at a time. Complete each collection fully before starting the next.

Step 0: Read Discovery Manifest

Read .discover.json from the project root:

{
  "apiName": "Umbraco Forms Management API",
  "swaggerUrl": "https://localhost:44324/umbraco/swagger/forms-management/swagger.json",
  "baseUrl": "https://localhost:44324",
  "collections": ["form", "form-template", "field-type", "folder"]
}

If an argument was provided, filter to only that collection. If .discover.json doesn't exist, tell the user to run npx @umbraco-cms/create-umbraco-mcp-server discover first.

Step 1: Check Generated Client

Check if src/umbraco-api/api/generated/ exists and contains .ts files. If not, run:

npm run generate

Then read the generated files to understand:

• The API client function name (e.g. getFormsManagementAPI)
• The available Zod schemas (in *.zod.ts files)
• The available client methods and their signatures