MCP servers are what make Claude genuinely useful for real work - they connect it to your files, your database, your issue tracker, your browser. But Claude Desktop stores them in one shared configuration file. So the moment you work across more than one project, every MCP server you add shows up everywhere, whether it belongs there or not.
Your client's database connector sitting in your personal Claude. A half-finished experimental server breaking an unrelated project. One giant claude_desktop_config.json that you're afraid to touch. This article shows how to give each project its own isolated set of MCP servers instead.
On Windows, Claude Desktop keeps its MCP servers in a single claude_desktop_config.json under its application data directory - one file, per user. That design is fine if you only ever do one kind of work. It falls apart when you don't:
Claude Desktop Manager gives each profile its own isolated data folder - which means its own claude_desktop_config.json, and therefore its own mcpServers. You edit them through a built-in JSON editor that validates as you type, and it only ever rewrites the mcpServers section of that profile's config. Your login session and every other profile stay untouched.
So you can run, at the same time:
Only mcpServers is touched. The editor rewrites just that block of the profile's config file. It never modifies your authentication or the rest of your settings - so testing a new server can't log you out or corrupt a working profile.
Most people converge on a standard toolkit - a filesystem server, a browser server, maybe a database connector. Recreating that by hand for every new project is tedious. The Seed feature solves it: create a new profile pre-loaded with another profile's MCP configuration (and Chrome-extension preference), but never its login. A new client instantly inherits your tooling, signs in with its own account, and stays completely isolated.
mcpServers and save - it applies only to this profile.If you also run Claude Code, the same isolation carries into the terminal - see running Claude Desktop and Claude Code with isolated configs. And if the goal is separate accounts entirely, start with running multiple Claude Desktop accounts at the same time.
Yes. With Claude Desktop Manager, each profile has its own isolated data folder, which includes its own MCP server configuration. You edit a profile's mcpServers through a built-in, validated JSON editor - changes apply only to that profile.
Claude Desktop keeps MCP servers in its claude_desktop_config.json file inside its application data directory. By default there is a single shared file per user. Claude Desktop Manager points each profile at its own data directory, so every profile gets its own claude_desktop_config.json and its own mcpServers block.
No. Each profile is isolated. The editor only rewrites the mcpServers section of that profile's own config file, leaving other profiles - and your login sessions - untouched.
Yes. The Seed feature creates a new profile pre-loaded with another profile's MCP setup (and Chrome extension preference), but never its login. It's the fastest way to give a new client or project your standard tooling without any credentials leaking across.
Claude Desktop Manager is free to download. Standard ($10, one-time purchase) unlocks 2 simultaneous instances with no time limit. Pro ($30, one-time) removes all limits and adds QuickPrompt and QuickAsk.