@1key4ai/cc-bridge

One install, every tool. The unified front door for 1K4 on Claude Code.

Plan review, advisors, brainstorm, the Studio Lab bridge, and the full lab workspace surface — all behind a single MCP server registration. Updates ship automatically via the @latest pin.

Setup

1. Get your API key at 1key4ai.com/claude-code
2. Run the setup command:

npx -y -p @1key4ai/cc-bridge@latest cc-bridge setup --api-key YOUR_KEY

This writes a single mcpServers["1k4-bridge"] entry to ~/.claude.json. Restart Claude Code and the full tool surface is available immediately.

For staging:

npx -y -p @1key4ai/cc-bridge@latest cc-bridge setup --api-key YOUR_KEY --api-base https://staging.1key4ai.com

To skip the migration prompt (e.g., in CI or scripted setups):

npx -y -p @1key4ai/cc-bridge@latest cc-bridge setup --api-key YOUR_KEY --yes

Migration from existing 1K4 packages

If you already have @1key4ai/mcp-review, @1key4ai/mcp-lab, or @1key4ai/mcp-studio installed (one or more of mcpServers["1k4-review"], mcpServers["1k4-lab"], mcpServers["1k4-studio"] in ~/.claude.json), cc-bridge setup detects them and offers to consolidate:

1. Detects existing 1k4-review/1k4-lab/1k4-studio entries and captures their env vars (your API key + API base).
2. Writes a timestamped backup ~/.claude.json.bak-<timestamp>.
3. Prints a summary of planned changes.
4. Prompts Proceed? [y/N] (skippable via --yes).
5. On confirm: removes the legacy entries and writes a single mcpServers["1k4-bridge"] with the captured env vars preserved.
6. Cleans up legacy mcp-lab hooks from ~/.claude/settings.json and removes the obsolete Lab Bridge block from your project's CLAUDE.md.

The migration is opt-in. If you don't run cc-bridge setup, your existing mcp-review / mcp-lab / mcp-studio installs keep working as-is — they get the same expanded tool surface via their @latest pin on next CC session start.

Tools included

The full unified surface (28 tools + the dynamic catalog):

• 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 (auto-refresh every 60s; new backend skills appear without restart)

How it works

After setup, mcpServers["1k4-bridge"] in ~/.claude.json looks like:

{
  "mcpServers": {
    "1k4-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@1key4ai/cc-bridge@latest"],
      "env": { "K4_API_KEY": "your-key", "K4_API_BASE": "https://1key4ai.com" }
    }
  }
}

Claude Code spawns the bridge as a stdio MCP server on each session. The @latest pin means npx checks the registry every spawn — when we publish a new bridge version, your next CC session picks it up automatically. No re-run of setup required.

Pricing

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

Troubleshooting

• cc-bridge setup reports ~/.claude.json is malformed: your ~/.claude.json has a JSON parse error. Fix the file manually (cat ~/.claude.json | python3 -m json.tool) and re-run setup.
• Setup hangs in CI / non-interactive shells: pass --yes to skip the prompt.
• Migration removed an entry I wanted to keep: check ~/.claude.json.bak-<timestamp> for the pre-migration state. The backup is byte-equivalent to the file before any cc-bridge mutation.