メニュー
Load MCP development patterns and best practices for building tools with the @umbraco-cms/mcp-server-sdk. Use when starting tool development or needing pattern reference.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/umbraco/Umbraco-MCP-Base --skill mcp-patternsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Build MCP tool collections from discovered API groups. Reads .discover.json and generates tools and collection registrations. Use after running 'npx @umbraco-cms/create-umbraco-mcp-server discover'.
Build integration tests for MCP tool collections. Reads .discover.json and creates test setup, builders, helpers, and test files per collection. Use after running '/build-tools'.
Add or update an LLM eval test for a specific tool or collection. Creates a new eval scenario or updates an existing one to cover new tools. Use when adding eval coverage for new or modified tools.
SKILL.md を表示中
| name | mcp-patterns |
| description | Load MCP development patterns and best practices for building tools with the @umbraco-cms/mcp-server-sdk. Use when starting tool development or needing pattern reference. |
This skill loads comprehensive patterns for building MCP tools using the @umbraco-cms/mcp-server-sdk.
Use this skill when:
All tools follow this structure:
import {
withStandardDecorators,
executeGetApiCall,
executeVoidApiCall,
createToolResult,
CAPTURE_RAW_HTTP_RESPONSE,
ToolDefinition,
} from "@umbraco-cms/mcp-server-sdk";
const MyTool = {
name: "tool-name",
description: "What the tool does",
inputSchema: zodSchema.shape,
outputSchema: responseSchema, // For GET operations
slices: ["read"], // Categorization
annotations: {
readOnlyHint: true,
: ,
: ,
},
: (params) => {
},
} <...>;
();
Configure once at server startup:
import { configureApiClient } from "@umbraco-cms/mcp-server-sdk";
import { getMyAPI } from "./api/generated/myApi.js";
configureApiClient(() => getMyAPI());
For GET operations that return data:
return executeGetApiCall<ReturnType<Client["method"]>, Client>(
(client) => client.method(params, CAPTURE_RAW_HTTP_RESPONSE)
);
For DELETE/PUT operations that return void:
return executeVoidApiCall<Client>(
(client) => client.deleteItem(id, CAPTURE_RAW_HTTP_RESPONSE)
);
For custom responses (typically CREATE operations):
if (response.status === 201) {
return createToolResult({ success: true, id: extractedId });
} else {
return createToolResultError(response.data);
}
Tools are categorized by operation type:
read - GET operationscreate - POST create operationsupdate - PUT operationsdelete - DELETE operationssearch - Search/filter operations| Operation | readOnlyHint | destructiveHint | idempotentHint |
|---|---|---|---|
| GET | ✅ | ❌ | ❌ |
| DELETE | ❌ | ✅ | ❌ |
| POST | ❌ | ❌ | ❌ |
| PUT | ❌ | ❌ | ✅ |
Important: DELETE is NOT idempotent (2nd call returns 404).
Umbraco APIs wrap references to other entities in a nested object — most commonly
parent: { id } or parent: { path }. Never expose that shape to the LLM: accept a flat
scalar (parentId, path) and rebuild the nested object inside the handler. See
references/schema-flattening.md for the full pattern, the when-to-apply matrix, and the rules.
src/
├── api/
│ ├── client.ts # API client with mock support
│ ├── openapi.yaml # OpenAPI spec
│ └── generated/ # Orval-generated client + Zod schemas
├── tools/
│ └── {entity}/
│ ├── get/
│ ├── post/
│ ├── put/
│ ├── delete/
│ └── index.ts # Collection export
└── index.ts # MCP server entry
Generate client and Zod schemas from OpenAPI:
npm run generate
Configuration in orval.config.ts:
client option){action}-{entity} patternwithStandardDecorators handles errors automaticallyparentId / path, rebuild parent: { id } /
parent: { path } in the handler (see Schema Flattening above, or references/schema-flattening.md for the full pattern)SOC 職業分類に基づく