cb-analytics-clusterlisted

Use this skill when the user wants to inspect or configure the Couchbase cluster itself — node membership, memory quotas, rebalance, auto-failover, system events, or just verifying that a cluster is reachable. Trigger when they mention "cluster info", "ping", "rebalance", "auto-failover", "system events", "nodes", "memory quota", or "who_am_i".
celticht32/Couchbase-Skills-for-Claude.ai · ★ 1 · AI & Automation · score 75

Install: claude install-skill celticht32/Couchbase-Skills-for-Claude.ai

# Cluster operations You have 9 cluster-level tools, mostly read-only. ## Reachability and identity - `ping_cluster(cluster)` — fast yes/no liveness check. Use this first when troubleshooting any other tool failure. - `get_cluster_info(cluster)` — UUID + implementation version. Cheap; safe to call often. - `who_am_i(cluster)` — what the cluster sees the current MCP user as (roles, domain). Useful when an `AnalyticsAuthError` shows up. ## Capacity and health - `get_cluster_details(cluster)` — nodes, memory quotas (`memoryQuota`, `cbasMemoryQuota`), `balanced`, `rebalanceStatus`. Read before any capacity decision. - `get_cluster_tasks(cluster)` — every in-flight task (rebalance, compaction, XDCR). Empty list is the happy path. - `get_rebalance_progress(cluster)` — focused view: rebalance only. Returns `{"status": "none"}` when nothing's running. ## Auto-failover - `get_auto_failover_settings(cluster)` — read current settings. - `configure_auto_failover(enabled, timeout, max_count, cluster)` — Couchbase recommends `enabled=True, timeout=120, max_count=1` for 3-node clusters; larger clusters can use `max_count=2+`. ## System events `get_system_events(since_time, cluster)` returns recent operational events (`info` / `warning` / `error`). `since_time` is an ISO 8601 timestamp; omit it for "everything the cluster will give us". Use this for post-incident triage: > User: "Why did the cluster fail over at 03:00?" > 1. `get_system_events(since_time="2026-05