JsonUI
InstallationInstall JsonUI in one lineOne command installs the CLI, the MCP server, and the agent pack into Claude Code.
shell
curl -fsSL https://raw.githubusercontent.com/Tai-Kimura/JsonUI-Agents-for-claude/main/installer/bootstrap.sh | bash
What gets installedThree artifacts land on your machine. You do not need to touch any of them directly.
CLIjsonui-cli~/.jsonui-cli/jui / sjui / kjui / rjui / jsonui-test / jsonui-doc. Ships shared/core/{attribute_definitions,component_metadata}.json for MCP to read directly.
MCPjsonui-mcp-server~/.jsonui-mcp-server/ + ~/.claude.json45 MCP tools across 6 groups (A:10 / B:7 / C:7 / D:9 / E:3 / F:9) with runtime-sync so the attribute schema is always current.
AgentsAgents + Skills + Rules./.claude/ + CLAUDE.md9 agents, 11 skills, and 5 rules, installed per project so Claude Code can launch the conductor on demand.
Because the CLI lives at ~/.jsonui-cli/, the MCP's 4-layer fallback's 3rd tier (home) resolves automatically. No environment variables are required.
PrerequisitesMissing items only skip the affected tool — the installer keeps going and prints a warning.
git and curlREQUIRED
All platformsNeeded by the bootstrap to fetch the CLI, MCP, and agent bundle.
Node.js (>= 20)REQUIRED
MCP server runtimeRuns the MCP server itself.
npmREQUIRED
MCP dependency installInstalls the MCP server's dependencies.
Ruby (>= 2.7)OPTIONAL
Native platform toolingOnly required if you will use sjui / kjui / rjui.
Python 3 (>= 3.10)OPTIONAL
Developer toolsOnly required if you will use jui / jsonui-test / jsonui-doc.
Three steps to a working environmentRun one command, add six PATH lines, restart Claude Code. That is the whole install.
1Run the one-liner
This single curl fetches the CLI, the MCP server, and the agent pack, and registers the MCP entry into Claude Code.
shell
curl -fsSL https://raw.githubusercontent.com/Tai-Kimura/JsonUI-Agents-for-claude/main/installer/bootstrap.sh | bash
2Add PATH lines and reload your shell
Bootstrap prints these PATH lines at the end. Paste them into ~/.zshrc (or your shell's equivalent) and reload.
~/.zshrc
cat >> ~/.zshrc <<'EOF'
# JsonUI CLI Tools
export PATH="$HOME/.jsonui-cli/jui_tools/bin:$PATH"
export PATH="$HOME/.jsonui-cli/document_tools:$PATH"
export PATH="$HOME/.jsonui-cli/test_tools:$PATH"
export PATH="$HOME/.jsonui-cli/sjui_tools/bin:$PATH"
export PATH="$HOME/.jsonui-cli/kjui_tools/bin:$PATH"
export PATH="$HOME/.jsonui-cli/rjui_tools/bin:$PATH"
EOF
source ~/.zshrc
3Restart Claude Code and say the magic words
Completely restart Claude Code and open your project. The SessionStart hook fires the conductor automatically — or invoke /jsonui at any time. The conductor greets you with the New work / Modify / Investigate / Backend menu.
Claude Code slash command
/jsonui
Verify it worksThree commands confirm each part of the install is reachable.
In your shell
jui --help
→ expect CLI usage output. If you see command-not-found, PATH is not set.
In Claude Code
Use the jui-tools MCP to list components
→ expect search_components to fire and return 27 components.
In Claude Code
/jsonui
→ expect the conductor agent to greet you with the four-option menu.
Updating is the same commandBootstrap is idempotent — rerun to pull the latest of every component. One step needs a follow-up: after the MCP server updates, restart Claude Code completely. A running server answers from its in-memory cache, so new tools and attributes do not appear until the restart.
shell
curl -fsSL https://raw.githubusercontent.com/Tai-Kimura/JsonUI-Agents-for-claude/main/installer/bootstrap.sh | bash
Each component is refreshed with git fetch + reset --hard origin/main, so local edits inside ~/.jsonui-cli or ~/.jsonui-mcp-server will be dropped.
Partial update (advanced)+
Custom install paths (advanced)+
Install components individually+
Uninstall+
TroubleshootingTap a symptom to see the cause and the fix.
▸jui: command not found
▸jui-tools does not appear in Claude Code's MCP list
▸MCP fails with 'attribute_definitions.json not found'
▸curl fails or returns 404
▸macOS reports 'node not found' even though Node is installed
▸Ruby or Python is reported as too old
Next: write your first screenYou have a working toolchain. Hello, JsonUI takes you from blank spec to text on screen in five minutes.