[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.

View original on GitHub ↗

4 Comments

xXMrNidaXx · 7 months ago

Great feature request — this would significantly improve multi-device workflows.

A few implementation considerations that might help shape the design:

Sync Strategy Options

  1. Account-bound centralized storage — Store configs in Anthropic's backend, synced on login. Simplest UX but requires backend changes and introduces latency on startup.
  1. Git-backed sync — Point to a git repo URL in account settings (e.g., github.com/user/.claude-mcp-config). Products clone/pull on startup. Fits existing dev workflows and enables version control.
  1. Hybrid approach — Simple servers sync via account, complex configs (secrets, local paths) stay local with merge logic.

Edge Cases to Consider

  • Local path references — MCP configs often reference local executables (~/scripts/my-mcp-server.py). These paths break across machines. Perhaps support ${HOME} or ${CLAUDE_CONFIG_DIR} variables?
  • Secrets handling — Some MCP servers need API keys. Account sync would need encrypted secret storage or reference to local secret files.
  • Conflict resolution — When local and synced configs differ (e.g., user modified locally), how should merge work? Git-style diff? Last-write-wins? Manual resolution?

Minimal MVP

If this ships incrementally, a simple first step could be:

{
  "mcpServers": {
    "_sync": "https://api.anthropic.com/user/mcp-config"
  }
}

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.

github-actions[bot] · 7 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/22648
  2. https://github.com/anthropics/claude-code/issues/27458

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

pcgotan · 7 months ago

Closing as duplicate of #22648 which covers account-level settings sync (including MCP servers) more broadly.

github-actions[bot] · 7 months ago

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.