Public docs

LaunchChair CLI is optional beside MCP.

Use MCP-only when you want LaunchChair tools inside an agent. Add the CLI when you want terminal diagnostics, project discovery, retry-safe project creation, and a simple way to start the local bridge.

JSON catalog Personalized setup

Agent API and MCP Docs

Agent API Docs

Hermes Agent Setup

MCP Setup Docs

CLI Setup

Codex Desktop Setup

Claude Desktop Setup

Choice

Users can choose MCP-only or CLI plus MCP.

The CLI does not replace the MCP setup. MCP-only is still enough for Codex, Claude, or Hermes to call LaunchChair tools. The CLI is a convenience layer for people who want command-line diagnostics, project lookup, project creation, bridge startup, and config snippets.

MCP-only: configure mcp-bridge-server.mjs in your desktop agent and call LaunchChair tools from chat.

CLI plus MCP: keep the MCP tools and also run launchchair-cli.mjs for doctor, projects, create, continue, run-once, bridge, and mcp-config.

Local bridge: use launchchair-cli.mjs bridge or local-bridge.mjs when LaunchChair UI Run with agent should be picked up automatically.

Install

Download the bridge bundle and CLI.

The standard bridge install downloads the MCP server, local bridge, runners, public AGENTS.md bootstrap file, and launchchair-cli.mjs. The CLI uses the same env vars as the MCP bridge.

mkdir -p "$HOME/launchchair-agent"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/local-bridge.mjs" -o "$HOME/launchchair-agent/local-bridge.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/launchchair-cli.mjs" -o "$HOME/launchchair-agent/launchchair-cli.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/mcp-bridge-server.mjs" -o "$HOME/launchchair-agent/mcp-bridge-server.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/runner-command.mjs" -o "$HOME/launchchair-agent/runner-command.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/codex-runner.mjs" -o "$HOME/launchchair-agent/codex-runner.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/claude-code-runner.mjs" -o "$HOME/launchchair-agent/claude-code-runner.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/chatgpt-runner.mjs" -o "$HOME/launchchair-agent/chatgpt-runner.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/claude-runner.mjs" -o "$HOME/launchchair-agent/claude-runner.mjs"
curl -fsSL "https://www.launchchair.io/agent-artifacts/AGENTS.md" -o "$HOME/launchchair-agent/AGENTS.md"
chmod +x "$HOME/launchchair-agent"/*.mjs
LAUNCHCHAIR_AGENT_WORKDIR="${LC_AGENT_CODEX_CWD:-${LC_AGENT_CLAUDE_CODE_CWD:-$PWD}}"
if [ -d "$LAUNCHCHAIR_AGENT_WORKDIR" ] && [ ! -f "$LAUNCHCHAIR_AGENT_WORKDIR/AGENTS.md" ]; then
  printf '%s\n' \
    '# LaunchChair Agent Bootstrap Pointer' \
    '' \
    'Before searching this repo, read ~/launchchair-agent/AGENTS.md.' \
    'Use LaunchChair MCP/API first for product phases, project discovery, project creation, and phase loops.' \
    'Do not ask for extra confirmation before using LaunchChair MCP/API when the user already requested the action and the token permits it.' \
    'Only inspect this repo for Stack Setup, Build MVP, Design/Landing Page, SEO implementation, smoke testing, security review, or code remediation.' \
    > "$LAUNCHCHAIR_AGENT_WORKDIR/AGENTS.md"
fi

Environment

Use the same token and project variables.

Create a token in Settings -> API Access. Put that token wherever your chosen client launches the bridge or CLI. A Hermes env file does not configure Codex Desktop; each client needs its own env surface.

LAUNCHCHAIR_BASE_URL="https://www.launchchair.io"
LAUNCHCHAIR_AGENT_TOKEN="<full lc_at token from Settings API Access>"
LAUNCHCHAIR_PROJECT_ID="PASTE_PROJECT_UUID_OR_LEAVE_BLANK_IF_AGENT_CREATES_PROJECT"

Leave LAUNCHCHAIR_PROJECT_ID blank when the agent should create or discover projects.

Set LAUNCHCHAIR_PROJECT_ID when you want the CLI or MCP server to default to one project.

Set LC_AGENT_CODEX_CWD or LC_AGENT_CLAUDE_CODE_CWD to an existing repo folder or an empty folder before Stack Setup.

Commands

Useful CLI commands.

The CLI is intentionally thin. It calls the Agent API for discovery and project creation, then uses the existing local bridge for queued runs.

node "$HOME/launchchair-agent/launchchair-cli.mjs" doctor
node "$HOME/launchchair-agent/launchchair-cli.mjs" projects --query LeafLore
node "$HOME/launchchair-agent/launchchair-cli.mjs" create --name SignalLift --one-liner "Distribution workspace for technical founders" --project-type b2b --problem "Founders do not know which channel message is working" --target-user "Seed-stage B2B SaaS founders" --solution "A guided launch workspace that turns proof points into channel campaigns" --idempotency-key signallift-v1
node "$HOME/launchchair-agent/launchchair-cli.mjs" continue --project-id PASTE_PROJECT_UUID --stop-phase-key market_validation
node "$HOME/launchchair-agent/launchchair-cli.mjs" run-once
node "$HOME/launchchair-agent/launchchair-cli.mjs" bridge
node "$HOME/launchchair-agent/launchchair-cli.mjs" mcp-config codex

Fresh projects

CLI helps when there is no repo yet.

LaunchChair can run Product Ideation, Market & Validation, Positioning & Pricing, and MVP Blueprint before a repository exists. For a fresh Codex project, point LC_AGENT_CODEX_CWD at an empty folder. Stack Setup can then guide the user through repo/provider setup and later build into that folder.

Use projects or create before searching the local repo.

Use install-agent-md to create a project-local pointer for fresh chats.

Use mcp-config to generate the correct Codex or Claude config with the current bridge path.

Machine-readable summary