Sekura Design MCP

Get paste-ready component code

get_component_code

Read-only

Get production code for a component in your chosen framework: ARIA-wired HTML, token-based CSS, or editable recipes with lifecycle wiring. Inspect metadata for dependencies and app 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

TableJSON 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

TableJSON 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.

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.8/5.0

Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already in annotations, the description adds meaningful behavioral detail: HTML output includes ARIA wiring, CSS is token-based, framework outputs are editable recipes with lifecycle wiring, and dependencies/application responsibilities must be considered. This goes beyond the annotations without contradicting them.

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

Conciseness5/5

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

The description is compact, well-structured across HTML/CSS and framework cases, and every sentence contributes useful information. There is no filler or repetition of schema details.

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?

Given the rich schema, output schema, and annotations, the description covers the essential behavior and responsibilities. It could be more complete by explicitly routing the agent away from get_component, but it is not missing critical invocation or safety information.

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%, so the parameters are already fully documented. The description adds only a high-level summary of framework behavior and does not introduce new parameter meaning beyond what the schema's framework enum already provides. Baseline 3 is appropriate.

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 tool returns production code for a component in a requested framework, with specific behavior for HTML, CSS, and framework options. It is specific about verb and resource, though it does not explicitly differentiate itself from the similarly named sibling get_component.

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?

The description implies when to use the tool through 'paste-ready component code' and gives a follow-up instruction to inspect implementation metadata. However, it does not explicitly state when to use this tool over alternatives like get_component, nor does it provide exclusions or when-not-to-use guidance.

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