cb-analytics-mcp-setuplisted

# cb-analytics-mcp setup You're helping the user bring up or tune a cb-analytics-mcp installation. This skill covers configuration, validation, and the operator CLI. ## Required env vars (server refuses to start without these) - `MCP_API_KEY` — bearer token for Claude. **Min 32 chars.** Generate: `python -c "import secrets; print(secrets.token_urlsafe(48))"` - At least one of: - **Single cluster**: `CB_ANALYTICS_HOST` and `CB_ANALYTICS_PASSWORD` - **Multi cluster**: `CB_ANALYTICS_CLUSTERS_FILE` pointing at a JSON array - If GUI is enabled (default): `GUI_SESSION_SECRET` (≥32 chars) and a non-default `GUI_PASSWORD`. ## Validation flow Always recommend `cb-analytics-mcp --check` before `make run`. It returns: - exit 0 + a `config_valid` log line on success - exit 2 + a list of human-readable errors on failure `--check` doesn't try to reach the cluster. To verify network reachability too, use the **dashboard's Test Connection button** after starting the server (or `cb-analytics-mcp tools call ping_cluster --offline`, see CLI section below). ## Single vs multi-cluster decision - **One Couchbase cluster.** Use env vars only. Simpler. - **More than one cluster** (prod, stage, dev), or **one cluster with separate credentials per tenant.** Use `CB_ANALYTICS_CLUSTERS_FILE`. The file is a JSON array; each entry has `name`, `host`, `username`, `password`, and optional `tls`, `mgmt_port`, `analytics_port`, `verify_ssl`, `timeout_seconds`, `max_retries`. See `co