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.json57 MCP tools across 8 groups (A:10 / B:7 / C:7 / D:9 / E:3 / F:10 / G:5 / H:6) with runtime-sync so the attribute schema is always current.
AgentsAgents + Skills + Rules./.claude/ (CLAUDE.md untouched)9 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.
Prerequisitesgit, curl, Node and npm are required — the bootstrap stops without them. A missing Ruby or Python only skips the tools that need it, with a warning.
git and curlREQUIRED
All platformsNeeded by the bootstrap to fetch the CLI, MCP, and agent bundle.
Node.js (>= 22)REQUIRED
MCP server runtimeRuns the MCP server itself.
npmREQUIRED
MCP dependency installInstalls the MCP server's dependencies.
Ruby (>= 3.2)OPTIONAL
Native platform toolingOnly required if you will use sjui / kjui / rjui. Each of them checks the Ruby it runs on at start and stops below 3.2 with one line naming the version it found (measured on Ruby 2.6: all three exit 1). Each tool carries its own pin, a .ruby-version beside it: 3.2.11. Under rbenv that pin is the one that counts, because rbenv reads the .ruby-version nearest the script it starts, not the one nearest the directory you run it from (measured with rbenv 1.3.2: a vendored rjui started from a directory pinned to 3.2.2 ran on its own pin, and when its own pin named a Ruby that was not installed it stopped with `rbenv: version … is not installed` before it started). So install the Ruby the tools pin. `jui sync_tool` says so when rbenv lacks it: `ruby pin: the tool's Ruby 3.2.11 (its .ruby-version) is not installed under rbenv, and rbenv stops the tool before it starts — run: rbenv install 3.2.11`. `jui sync_tool` also writes the tools' pin into a platform directory that has none, only when that Ruby is installed under rbenv, and it does not rewrite a pin that is there: one below 3.2 is named and left for you to change (measured: a 2.7.0 pin was kept and named). That pin is what a Ruby started in the platform directory sees.
Python 3 (>= 3.11)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 shows the workflow menu — New work / Modify / Investigate / Backend — at the start of every session, and /jsonui shows it again at any time. Picking 1–3 launches the conductor.
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 the matching components.
In Claude Code
/jsonui
→ expect the four-option workflow menu; pick 1–3 and the conductor agent takes over.
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.