get_install_plan
read-onlyWalks registryDependencies depth-first, in the same order as the CLI. This is a plan, not an install. 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. |
| names | string[] | Required. At least one component name; use names, not name. |
| targetDir | string | Default src/components/jabkit |
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_install_plan",
"arguments": {
"brief": {
"intent": "Photography portfolio for art directors; show projects and invite enquiries.",
"visualDirection": "Restrained editorial layout with supplied photography; avoid dashboard chrome."
},
"names": [
"button"
]
}
}'Response 200
{
"filesToCreate": [ ".../button/Button.tsx", … ],
"filesToOverwrite": [], // always empty
"npmDeps": [ "clsx", "tailwind-merge" ],
"cssVars": { "light": {}, "dark": {} }
}Errors
- 400
{ "error": "names: names is required and must be a non-empty array of component names; …" } - 400
{ "error": "Unknown component: …" }