redshift-switch-profile

Redshift Switch Profile

Flip the active Redshift profile pointer file at ~/.config/redshift-comment-mcp/active-profile. No connection field re-entry: this skill assumes the target profile is already configured (host / user / dbname in config.toml + password in OS keychain).

For single-profile users (the majority) this skill is intentionally a no-op — see "When NOT to Use".

When to Use

• User has 2+ configured Redshift profiles and wants to switch which one the MCP server connects to.
• User invokes /redshift-switch-profile <name> (direct form).
• User invokes /redshift-switch-profile (interactive — lists profiles, asks which one).
• User says "switch to dev cluster" / "切換到 prod" / "クラスタを切替" with multiple clusters configured.

When NOT to Use

• Only default (or only one profile total) → friendly bow-out, suggest /redshift-setup <name> to add a second cluster.
• Zero profiles → suggest /redshift-setup to set up first cluster.
• User wants to set up a NEW profile → use /redshift-setup.
• User wants to change a profile's host / user / dbname → use /redshift-setup <name> (it offers existing values as defaults).
• User wants to change ONLY a password → use set-password CLI.

Storage Model

This skill only edits the active-profile pointer file:

Pointer file state	Effect on MCP server startup
Absent	Server falls back to "default" (canonical single-profile state)
Present, content = <name>	Server connects with <name>
Present, content = "default"	Unusual; this skill normalizes by removing the file instead of writing "default"

Connection fields (host / user / dbname / password) and [profile.<name>] blocks in config.toml are never touched by this skill.

Flow

Step 1 — Locate plugin install path

PLUGIN_ROOT=$(ls -d "$HOME/.claude/plugins/cache/redshift-comment-mcp/redshift-comment-mcp"/*/ 2>/dev/null | sort -V | tail -1)
test -n "$PLUGIN_ROOT" || { echo "Plugin not installed." >&2; exit 1; }
echo "$PLUGIN_ROOT"