ClaudeProfileSwitch
Zero-Dependency Python CLI for Claude Code & Claude Desktop

Stop fighting Claude Code profiles.
Switch accounts, MCP configs & track quota burn in 1 command.

Claude Code lacks multi-account/MCP profile switching across work and personal projects and gives no local warning before 5-hour session limits hit. ClaudeProfileSwitch snapshots isolated configs, auto-switches via .claude-profile, and monitors JSONL token burn locally.

The Old Painful Way

  • • Logging out and re-authenticating every time you swap work vs. personal Claude accounts
  • • Hand-editing claude_desktop_config.json or hardcoding client MCP API secrets per repo
  • • Getting hit mid-refactor by an unexpected 5-hour Claude Max/Pro session limit

With ClaudeProfileSwitch

  • • Snapshot & switch isolated ~/.claude.json + MCP server bundles in one CLI call
  • • Repo-bound .claude-profile auto-switching with ${ENV_VAR} MCP secret injection
  • • Instant 5-hour JSONL token burn audit with exhaustion ETA & CSV reporting

Up and running in 60 seconds

STEP 1

Snapshot Profiles

Run claude-profile-switch save --name work and save --name personal.

STEP 2

Swap & Inspect Burn

Run claude-profile-switch switch --name work and quota anytime.

STEP 3

Unlock Pro Automation

Run --activate YOUR_KEY for unlimited client profiles, .claude-profile env injection, & CSV exports.

Simple, one-time pricing

Free Starter

€0

Ideal for switching between work and personal accounts.

  • ✓ Save & switch up to 2 named profiles
  • ✓ Basic 5-hour session token count check
  • ✓ Zero external dependencies, runs 100% locally
Download Free CLI

Pro License

€24 once

Delivered instantly via Stripe Managed Payments license key.

  • ✓ Unlimited client, staging & personal profiles
  • ✓ Per-repo .claude-profile auto-switch & ${ENV_VAR} MCP injection
  • ✓ 5-hour burn-rate exhaustion ETA + CSV export & 7-day offline cache
Buy Pro License Key

FAQ

Does ClaudeProfileSwitch upload my auth tokens or transcripts?

Never. Profile snapshots, MCP configs, and JSONL log scanning happen strictly on your local filesystem. Only Pro license activation talks to the verification endpoint.

How does license activation work?

After Stripe Checkout, copy your Checkout Session key (cs_live_...) from the confirmation page and run claude-profile-switch --activate YOUR_KEY. Verified keys stay cached offline for 7 days.

Support & Contact

Operated by Stijn Dom (@domstijn).

Email: dom.stijn99@gmail.com

Issues: GitHub Support Tracker

14-Day Refund Policy

All Pro licenses include a 14-day no-questions-asked refund guarantee. Email dom.stijn99@gmail.com with your order ID for a full refund.

Terms & Privacy

All tools run locally in your browser, CLI, or editor. Zero PRDs, source code, or API keys are transmitted to third-party servers. Payments are processed securely by Stripe.