What problem does it solve?
Switching between multiple brand clients can accidentally point requests at the wrong ad account or analytics workspace, causing misrouted spend, incorrect reporting, or cross-client data leakage.
Core Features & Use Cases
- Multi-client credential switching with guardrails: Moves the active brand and active credential profile together so downstream MCP/platform operations use the correct client.
- Quick or full validation of access: Checks env vars and token validity (quick mode) or performs live connectivity/token checks (full mode) before proceeding.
- Operational safety checks: Detects in-progress executions that could be disrupted by a context switch and warns with specifics.
- Audit-ready switch logging: Writes a timestamped entry to a switch log including previous/new brand, validation results, and any warnings for traceability.
- Use case: An agency managing monthly reporting for Acme and running paid media for Beta can switch credentials, validate required integrations, and then generate accurate reports without risking cross-account actions.
Quick Start
Use credential-switch to switch to brand slug AcmeCorp and run quick validation by requesting: Switch brand credentials to AcmeCorp.