Skip to Content

DocsMore

Comparison

How turno compares with tools that switch accounts, manage MCP config or draw a status line.

View source

This page helps you decide whether you need turno or one of the tools that do a single part of it well.

Accounts per folderSeveral agentsShared MCP processesStatus lineNotes
turnoyesClaude Code, Codex, Copilot CLI, Cursor CLIyes, lazyyesCLI, local only
claude-swapswitch, not per folderClaude Codenonousage dashboard, parallel sessions
clauthswitchClaude CodenonoTUI, cross-account delegation
cc-switchnomanyno (manages MCP config)nodesktop app, provider switching
ccstatuslinenoClaude Codenoyesthe most customizable status line
MetaMCP, mcp-proxynoany MCP clientaggregates or bridgesnoDocker / transport bridge
Plain CLAUDE_CONFIG_DIRby handonenonowhat turno automates

If you only need one of these pieces, those tools are good at it. turno is for the case where you run many sessions of several agents with more than one account.

Which one fits

  • You want a different account per repository, picked for you. That is turno's folder rules: turno profile assign ~/code/acme work, then turno auto.
  • You only want to switch one Claude Code account for another. An account switcher is simpler.
  • You only want a status line. A dedicated status line tool gives you more to customize.
  • You want one endpoint that aggregates MCP servers for any client. An MCP aggregator or bridge does that; turno's gateway adds starting servers lazily, sharing them between sessions and stopping them when idle.
  • You have one account and one agent. A plain CLAUDE_CONFIG_DIR may be all you need; the gateway still helps if many sessions run the same servers.

What turno automates

Without turno, a second account is a second config folder that you point the agent at by hand:

CLAUDE_CONFIG_DIR=~/.claude-work claude

With turno, a folder rule and one command do it, for four agents:

turno profile assign ~/code/acme work
cd ~/code/acme && turno auto

On this page