@fizzgig-ai/install

One-command Fizzgig installer for AI editors. Auto-detects which MCP-aware editor you have, asks for your Fizzgig API key, and writes the right config to the right file.

Usage

npx @fizzgig-ai/install

That's it. The installer:

1. Detects which editors are present (Claude Code · Cursor · Windsurf · VS Code Copilot Chat · Continue.dev)
2. Asks which to install Fizzgig into (multi-select if you have several)
3. Asks for your Fizzgig API key (mint one at https://fizzgig.ai/dashboard/keys)
4. Writes the config to the right file per editor — preserving any other MCP servers you already have
5. Tells you exactly how to reload the editor so the new server is picked up

If Fizzgig is already configured in an editor, the installer asks before overwriting.

What it writes

Each editor expects a slightly different config shape. The installer knows them all:

| Editor | Config file | Field nuance | |---|---|---| | Claude Code | ~/.claude/settings.json | type: "http" required (else falls back to stdio and fails) | | Cursor | ~/.cursor/mcp.json | URL only — Cursor auto-detects HTTP transport | | Windsurf | ~/.codeium/windsurf/mcp_config.json | serverUrl not url | | VS Code (Copilot Chat) | ~/.vscode/mcp.json | servers (top-level), not mcpServers | | Continue.dev | ~/.continue/config.json | Lives under experimental.modelContextProtocolServers (array, not map) |

Privacy

The installer never sends your API key anywhere — it stays on your machine, written only to the local config file you'd manually edit anyway. No network calls except to verify the registry URL is reachable (and even that only for diagnostic output).

Troubleshooting

"No supported MCP-aware editors detected" — your editor's config dir isn't where we expect. Check the manual install snippets at https://fizzgig.ai/dashboard/keys instead.

"That looks too short — please paste the full key" — a Fizzgig API key looks like fz_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. You only see the plaintext key once, at creation time. Lost it? Mint a new one and revoke the old.

Editor doesn't see Fizzgig after install — the installer prints the reload step per editor. Some editors watch the config file, some require a full restart. Try a restart if a reload doesn't pick it up.

Source

This package is part of the Fizzgig monorepo: https://github.com/RascalRebelCreative/fizzgig/tree/main/packages/install