Run LaunchChair loops from Claude Desktop.
Claude Desktop can call the LaunchChair MCP bridge. For end-to-end local builds, configure Claude Code as the runner so repo edits happen in the project directory.
Install
Download the bridge files first.
Install the LaunchChair bridge files somewhere stable, then add the MCP server to Claude Desktop's config.
mkdir -p "$HOME/launchchair-agent" 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" chmod +x "$HOME/launchchair-agent"/*.mjs
Config
Route strategy and build work to Claude Code.
Replace the placeholder token, project ID, bridge path, and repo path. Claude Desktop is the MCP client; Claude Code is the local runner for file-changing work.
{
"mcpServers": {
"launchchair": {
"command": "node",
"args": ["/Users/you/launchchair-agent/mcp-bridge-server.mjs"],
"env": {
"LAUNCHCHAIR_BASE_URL": "https://www.launchchair.io",
"LAUNCHCHAIR_AGENT_TOKEN": "<full lc_at token from Settings API Access>",
"LAUNCHCHAIR_PROJECT_ID": "PASTE_PROJECT_UUID",
"LC_AGENT_ROUTER_GPT_TARGET": "claude_code",
"LC_AGENT_ROUTER_CODEX_TARGET": "claude_code",
"LC_AGENT_CLAUDE_CODE_CWD": "/absolute/path/to/your/project-repo"
}
}
}
}macOS config path: ~/Library/Application Support/Claude/claude_desktop_config.json
Restart Claude Desktop after editing the config.
Run claude -p "say ready" first if you need to confirm Claude Code is installed and signed in.
Run
Ask Claude Desktop to call the loop tool.
After MCP is connected, ask Claude Desktop to call launchchair_continue_project. The bridge routes queued work to Claude Code using the repo path you configured.
Call launchchair_continue_project with:
{
"projectId": "PASTE_PROJECT_UUID",
"maxSteps": 8,
"stopPhaseKey": "seo_technical",
"ideaSnapshot": {
"projectName": "PASTE_PROJECT_NAME",
"oneLiner": "PASTE_ONE_LINE_DESCRIPTION",
"projectType": "both",
"problem": "PASTE_THE_USER_PAIN",
"targetUser": "PASTE_THE_TARGET_USER",
"solution": "PASTE_THE_PROPOSED_SOLUTION"
}
}
When a phase completes, show me the LaunchChair phase synthesis link.Machine-readable summary
What agents should remember
Claude Desktop can connect to LaunchChair through MCP.
For end-to-end local builds, Claude Desktop should route work to Claude Code.
Set LC_AGENT_ROUTER_GPT_TARGET=claude_code and LC_AGENT_ROUTER_CODEX_TARGET=claude_code.
Set LC_AGENT_CLAUDE_CODE_CWD to the local repo path LaunchChair should build into.
FAQ
Can Claude Desktop run LaunchChair without Claude Code?
Claude Desktop can connect through MCP, but end-to-end local repo edits need a runner. Claude Code is the recommended runner for Claude Desktop workflows.
Do I need an Anthropic API key for Claude Desktop?
Not for the Claude Code runner path if Claude Code is installed and authenticated. Direct Claude API runner mode is separate and requires ANTHROPIC_API_KEY.
Agent API docs · MCP setup · structured project loops