Sekura Design MCP

Get paste-ready component code

get_component_code

Read-only

Retrieve production code for a Sekura Design System component in your chosen framework, including markup, styles, and lifecycle wiring. Inspect metadata for dependencies and responsibilities.

Instructions

Production code for a component in the requested framework. HTML returns reference markup with the required ARIA wiring; CSS returns the production stylesheet written against semantic tokens; framework options return editable reference recipes with native markup and lifecycle wiring. Inspect implementation metadata for dependencies and application responsibilities.

Input Schema

Name	Required	Description	Default
`id`	Yes	Component id.
`framework`	Yes	html: Reference markup. Load sekura.css and the behaviour bundle, then call Sekura.enhance(). \| css: Component CSS. Read implementation.cssDependencies for required child styles, or load sekura.css. \| react: React TypeScript reference recipe with native markup, unique IDs, editable children and controller cleanup. \| vue: Vue reference recipe with native markup, slots and controller cleanup. \| svelte: Svelte reference recipe with native markup, snippets and controller cleanup. \| angular: Angular standalone reference component with native markup and controller cleanup. \| blazor: Blazor reference component. Requires the IIFE bundle and the documented JS lifecycle bridge. \| web-component: Light-DOM reference element with native markup and controller cleanup.

Output Schema

Name	Required	Description	Default
`code`	Yes
`version`	Yes
`framework`	Yes
`componentId`	Yes
`schemaVersion`	Yes
`implementation`	Yes
`initialization`	Yes
`requiredStylesheets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv3.2.1Oct 18, 2026

addedOutput schema / properties / implementation / properties / designKit
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / implementation / properties / runtime / properties / capabilities
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

addedOutput schema / properties / implementation / properties / runtime / properties / identity

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "attribute": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "requiredFor": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "attribute",
+    "requiredFor",
+    "description"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / implementation / properties / runtime / properties / purposes

Added value: +{
+  "items": {
+    "enum": [
+      "navigation",
+      "commands",
+      "disclosure",
+      "selection"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / implementation / properties / runtime / properties / requirements

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "autoMarker": {
+        "type": "string"
+      },
+      "controller": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "manualOnly": {
+        "type": "boolean"
+      },
+      "when": {
+        "additionalProperties": false,
+        "properties": {
+          "attribute": {
+            "type": "string"
+          },
+          "className": {
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "required": [
+      "controller",
+      "when",
+      "description"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / implementation / properties / runtime / properties / stateOwnership

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "application": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "controller": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "controller",
+    "application"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / implementation / required

Previous value: -[
-  "runtime",
-  "rootClass",
-  "cssDependencies",
-  "svgSymbols",
-  "controller",
-  "behavior",
-  "frameworkOutput",
-  "applicationResponsibilities",
-  "events",
-  "autoMarker",
-  "nativeReactExport"
-]New value: +[
+  "runtime",
+  "rootClass",
+  "cssDependencies",
+  "svgSymbols",
+  "controller",
+  "behavior",
+  "frameworkOutput",
+  "applicationResponsibilities",
+  "events",
+  "autoMarker",
+  "nativeReactExport",
+  "designKit"
+]

Changed2 schema fields changedv3.0.0Oct 3, 2026

addedOutput schema / properties / implementation / properties / runtime

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "autoSelectors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "controllers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "manualOnly": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "controllers",
+    "autoSelectors",
+    "manualOnly",
+    "notes"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / implementation / required

Previous value: -[
-  "rootClass",
-  "cssDependencies",
-  "svgSymbols",
-  "controller",
-  "behavior",
-  "frameworkOutput",
-  "applicationResponsibilities",
-  "events",
-  "autoMarker",
-  "nativeReactExport"
-]New value: +[
+  "runtime",
+  "rootClass",
+  "cssDependencies",
+  "svgSymbols",
+  "controller",
+  "behavior",
+  "frameworkOutput",
+  "applicationResponsibilities",
+  "events",
+  "autoMarker",
+  "nativeReactExport"
+]

Changed3 schema fields changedv2.1.0Sep 8, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / framework / description

Previous value: -"html: Reference markup with the required ARIA wiring in place. | css: The production stylesheet for this component, written against semantic tokens. | react: TypeScript React component with forwardRef and typed variant props. | vue: Vue 3 single-file component using the composition API. | svelte: Svelte 5 component using runes. | angular: Angular standalone component. | blazor: Blazor Razor component with typed parameters. | web-component: Framework-free custom element wrapping the same classes."New value: +"html: Reference markup. Load sekura.css and the behaviour bundle, then call Sekura.enhance(). | css: Component CSS. Read implementation.cssDependencies for required child styles, or load sekura.css. | react: React TypeScript reference recipe with native markup, unique IDs, editable children and controller cleanup. | vue: Vue reference recipe with native markup, slots and controller cleanup. | svelte: Svelte reference recipe with native markup, snippets and controller cleanup. | angular: Angular standalone reference component with native markup and controller cleanup. | blazor: Blazor reference component. Requires the IIFE bundle and the documented JS lifecycle bridge. | web-component: Light-DOM reference element with native markup and controller cleanup."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "componentId": {
+      "type": "string"
+    },
+    "framework": {
+      "enum": [
+        "html",
+        "css",
+        "react",
+        "vue",
+        "svelte",
+        "angular",
+        "blazor",
+        "web-component"
+      ],
+      "type": "string"
+    },
+    "implementation": {
+      "additionalProperties": false,
+      "properties": {
+        "applicationResponsibilities": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "autoMarker": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "behavior": {
+          "enum": [
+            "native",
+            "controller",
+            "application"
+          ],
+          "type": "string"
+        },
+        "controller": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "cssDependencies": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "events": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "applicationRequired": {
+                "type": "boolean"
+              },
+              "detail": {
+                "additionalProperties": {
+                  "type": "string"
+                },
+                "propertyNames": {
+                  "type": "string"
+                },
+                "type": "object"
+              },
+              "name": {
+                "type": "string"
+              },
+              "source": {
+                "enum": [
+                  "native",
+                  "controller"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "detail",
+              "source",
+              "applicationRequired"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "frameworkOutput": {
+          "const": "reference-recipe",
+          "type": "string"
+        },
+        "nativeReactExport": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "rootClass": {
+          "type": "string"
+        },
+        "svgSymbols": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "rootClass",
+        "cssDependencies",
+        "svgSymbols",
+        "controller",
+        "behavior",
+        "frameworkOutput",
+        "applicationResponsibilities",
+        "events",
+        "autoMarker",
+        "nativeReactExport"
+      ],
+      "type": "object"
+    },
+    "initialization": {
+      "type": "string"
+    },
+    "requiredStylesheets": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "schemaVersion": {
+      "const": 1,
+      "type": "number"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "version",
+    "componentId",
+    "framework",
+    "code",
+    "implementation",
+    "requiredStylesheets",
+    "initialization"
+  ],
+  "type": "object"
+}

First observedv1.0.0Aug 5, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: which outputs are reference vs production, that framework recipes are editable and include lifecycle wiring, and that implementation metadata should be inspected for dependencies/application responsibilities. It stops short of describing pagination or response shape, but for a read tool this is good added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core return value, then a per-format breakdown, then a follow-up instruction. Little waste, though the format breakdown overlaps with the framework enum descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, yet it gives enough context to choose a framework and understand what each yields. Both required params are documented and the read-only nature is covered. Complete for an agent to invoke correctly; only the sibling-routing guidance is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including an extensive per-enum description for framework, so the schema carries the parameter burden and baseline is 3. The description's HTML/CSS/framework characterizations largely restate what the enum already documents, adding framing rather than new syntax or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the resource and scope: production/reference code for a component, parameterized by framework. It distinguishes the output flavors (HTML reference markup, CSS production stylesheet, framework recipes) so an agent knows what it gets. It does not, however, name or differentiate from the sibling get_component metadata tool, leaving that distinction to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: request this when you need paste-ready code for a given framework. There is no explicit when-to-use vs get_component, get_behavior, or get_pattern, and no stated prerequisites or exclusions. The per-framework output notes help an agent understand results but not tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.