@1key4ai/mcp-lab

1K4 Lab bridge for Claude Code. Persistent connection from Claude Code to a 1K4 Studio session, with the full unified tool surface.

Setup

1. Get a single-use setup token at 1key4ai.com/install (10-minute TTL; exchanged for your API key locally, so your long-lived key never goes on the command line).
2. Run the setup command:

npx -y -p @1key4ai/[email protected] mcp-lab setup --setup-token <token>

This registers the MCP server, installs the Lab message hooks, and starts a persistent bridge daemon that survives terminal close and (platform-dependent) reboot. The install is pinned to an exact version; rerun mcp-lab setup to move to a newer release.

For staging:

npx -y -p @1key4ai/[email protected] mcp-lab setup --setup-token <token> --api-base https://staging.1key4ai.com

Legacy: --api-key sk-... is still accepted for backward compatibility, but the setup-token flow is preferred so a long-lived key never lands in shell history or process lists.

What happens

After setup, two things are wired up:

• The 1K4 Lab in your browser can talk directly to Claude Code via the bridge daemon. Switch to Claude Code mode in any Lab session and your messages route to CC.
• Claude Code gains the full 1K4 tool surface (plan review, advisors, brainstorm, Studio agent control, Lab workspace operations).

Tools included

Same full unified surface as cc-bridge:

• Plan review: 1k4_review_plan
• Advisors: 1k4_advisors, 1k4_consult, 1k4_brainstorm
• Studio bridge: 1k4_send_message, 1k4_wait_for_message, 1k4_get_session_status, 1k4_list_files, 1k4_get_file, 1k4_answer_questionnaire
• Lab workspace: lab_create_file, lab_edit_file, lab_read_file, lab_list_files, lab_create_folder, lab_move_file, lab_create_document, lab_edit_document, lab_create_presentation, lab_create_mockup, lab_git, lab_review_document, lab_update_file, lab_vm_ops, lab_deploy, lab_questionnaire, lab_web_fetch, lab_data_analysis
• Plus dynamically-discovered tools from the backend catalog

Subcommands

• mcp-lab setup --setup-token <token>: install + start daemon (legacy --api-key sk-... still accepted)
• mcp-lab stop: uninstall the OS-level service manager entry for the daemon
• mcp-lab bridge: manually run the bridge process (the daemon does this automatically). The daemon respawns the pinned version; it does not auto-upgrade — rerun mcp-lab setup to update.

New users: try cc-bridge for a single unified install

If you're starting fresh and want a single install entry instead of 1k4-lab, use @1key4ai/cc-bridge — same tool surface, single mcpServers["1k4-bridge"] entry. Existing mcp-lab users keep working as-is; cc-bridge setup opt-in consolidates.

Pricing

Pay per token at below list price. Credits never expire. Your first review is free.