Install
$ agentstack add mcp-sypnose-cloud-claude-desktop-multi ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Claude Desktop Multi-Instance (Windows)
Run multiple Claude Desktop instances side by side on Windows, each with its own account, MCP servers, and settings — even though Claude ships as a single-instance MSIX app.
One click. Survives auto-updates. Doesn't touch your normal install.
Why this is needed
Claude Desktop for Windows installs as an MSIX package under C:\Program Files\WindowsApps. That causes two problems if you want a second instance:
- Windows blocks launching the
.exedirectly fromWindowsApps
("Windows cannot access the specified device, path, or file"). So shortcuts pointing straight at the packaged exe fail.
- The package is built to run one instance. Even with Electron's
--user-data-dir flag, you can't reach the exe to pass it.
The fix: copy Claude to a normal folder outside WindowsApps (C:\ClaudePortable), where Windows allows direct launch, then create one shortcut per instance — each with its own --user-data-dir. Each instance gets a fully isolated profile: separate account, separate MCP servers, separate Cowork/settings.
> This is the part most guides miss: on Windows the MSIX exe can't be launched > in place, so you have to run a portable copy. That's exactly what install.ps1 > does, and re-running it picks up Claude's latest auto-update.
Quick start
- Download this repo (green
Codebutton →Download ZIP, then extract).
Or git clone https://github.com/radelqui/claude-desktop-multi.
- Double-click
INSTALL.cmd. It asks for Administrator (needed once, to
read the protected WindowsApps folder) and sets up 2 extra instances.
- On your Desktop you'll now have
Claude 2andClaude 3shortcuts.
Want a different number? Run from an admin PowerShell:
powershell -ExecutionPolicy Bypass -File scripts\install.ps1 -Instances 3
Logging into different accounts (important!)
The first login of each new instance must be done one at a time, with the other Claude windows closed.
Why: Claude's login opens your browser and returns to the app via a claude:// link. That link goes to whichever instance is currently open — so if several are open, the login lands on the wrong one and they all end up on the same account.
Do this:
- Close all Claude Desktop windows (check the system tray ▲ near the clock).
- Open only
Claude 2→ log in (Google sign-in, or email + code — any
method works) → finish the login.
- Open
Claude 3→ log in with a different account. - Open your normal Claude (Start menu) → it keeps your main account.
After the first login, each session persists. You can then run all of them at once, in any order.
Updating
When Claude Desktop auto-updates, the portable copy stays on the old version. To refresh it, just run INSTALL.cmd again (or scripts\install.ps1). It detects the new version, recopies, and your existing Desktop shortcuts keep working — no need to recreate them.
Uninstall
powershell -ExecutionPolicy Bypass -File scripts\uninstall.ps1
Removes the portable copy, the Claude N shortcuts, and the isolated profiles. Your normal Claude install is left untouched. Add -KeepProfiles to keep your logged-in instance data.
What gets created
| Path | What | |------|------| | C:\ClaudePortable\ | Portable copy of Claude (launchable, outside WindowsApps) | | %APPDATA%\Claude-Instance2, ...3, ... | Isolated profile per instance (account, MCP, settings) | | Desktop\Claude 2.lnk, Claude 3.lnk | Shortcuts that launch each instance |
Your normal install and its data (%APPDATA%\Claude) are never modified.
How it works (technical)
Get-AppxPackage *Claude*finds the current MSIX install location (robust
across version bumps).
robocopy /MIRmirrors…\appintoC:\ClaudePortable.- Each shortcut runs
C:\ClaudePortable\Claude.exe --user-data-dir="%APPDATA%\Claude-InstanceN". - Electron stores all per-instance state (auth tokens included) under that
data dir, so instances are fully independent.
Notes & limitations
- Windows only. On macOS use
open -n -a "Claude.app" --args --user-data-dir=...;
on Linux invoke the AppImage/binary with the same flag — no portable copy needed there.
- Re-run after each Claude update to keep the portable copy current.
- RAM: each instance is a full Electron app. Don't open more than you need.
- Not affiliated with Anthropic. Use at your own discretion.
License
MIT — do whatever you want. PRs welcome.
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sypnose-cloud
- Source: sypnose-cloud/claude-desktop-multi
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.