get_component
read-onlyReturns the complete {name}.json document: files, examples, dependencies, and metadata. Without both brief answers, returns status: "needs_brief" and discovery questions instead of this result. Answer from existing context, ask the user only for material gaps, and retry with the same brief on every call.
Arguments
| Name | Type | Notes |
|---|---|---|
| brief | { intent?: string; visualDirection?: string } | Both answers are needed for catalogue data: what you are building, for whom, and the desired action; then the brand's tone, references, assets, and styles to avoid. Missing/blank answers return questions. Reuse across this task. |
| name | string | Required |
| withExamples | boolean | false replaces examples with [] |
Direct HTTP request
These examples use the original JSON API. Connected MCP clients call this tool through tools/call; results arrive as JSON text in content. Invalid arguments return a tool error in MCP or HTTP 400 in this API.
curl -X POST https://jabkit.joseadrianbuctuanon.dev/mcp \
-H "Content-Type: application/json" \
-d '{
"tool": "get_component",
"arguments": {
"brief": {
"intent": "Photography portfolio for art directors; show projects and invite enquiries.",
"visualDirection": "Restrained editorial layout with supplied photography; avoid dashboard chrome."
},
"name": "button"
}
}'Response 200
{
"name": "button",
"files": [ { "path": "button/Button.tsx", … } ],
"registryDependencies": [],
"examples": [ … ]
}Errors
- 404
{ "error": "Not found" }