[Feature Request] Account-level MCP server configuration that syncs across devices and products
Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Feb 28, 2026 · closed Feb 28, 2026
Currently, MCP server configurations are stored locally and separately for each product (Claude Code CLI, Claude Desktop, Claude.ai browser). If a user sets up MCP servers on one machine or product, they have to manually reconfigure them everywhere else.
Request: Support an account-level MCP server configuration that is tied to the user's Anthropic account, so MCP servers sync automatically across:
- Different machines (e.g., work laptop vs personal)
- Different products (Claude Code CLI, Claude Desktop, Claude.ai)
This would eliminate the need to maintain duplicate configs in ~/.claude.json, claude_desktop_config.json, and the browser UI separately.
4 Comments
Great feature request — this would significantly improve multi-device workflows.
A few implementation considerations that might help shape the design:
Sync Strategy Options
github.com/user/.claude-mcp-config). Products clone/pull on startup. Fits existing dev workflows and enables version control.Edge Cases to Consider
~/scripts/my-mcp-server.py). These paths break across machines. Perhaps support${HOME}or${CLAUDE_CONFIG_DIR}variables?Minimal MVP
If this ships incrementally, a simple first step could be:
Products check the sync URL on startup (with reasonable caching), merge with local overrides. Users manage their config via a web UI on claude.ai.
Would love to see this happen — maintaining configs across CLI, Desktop, and browser is friction I'd happily eliminate.
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Closing as duplicate of #22648 which covers account-level settings sync (including MCP servers) more broadly.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.