Resolve MCP conflicts
Resolve one MCP difference at a time.
The same server name can hide different commands, credentials or scopes. Start by identifying which copy is trusted and which direction should change. A client launcher already pointing at this Hub may need no replacement.
Import updates Hub. Delivery updates the named client. Matching names alone do not make settings equivalent.
Make the direction of the change clear.
Recognize Hub connections
A launcher that already targets this Hub is a connection to the shared definition. A different Node or package path alone is not a reason to import that launcher as an original server.
Compare real differences
Review program, arguments, environment and scope. Private values are hidden; do not assume hidden credentials are identical simply because the visible text looks similar.
Keep intentional differences
A client may need its own settings. You can retain that difference rather than forcing unrelated scopes or credentials into one canonical copy.
Choose the source, then the destination.
Inspect one server
Open All data → MCP servers and select the item. Check the Hub copy, each client copy and whether the entry already uses this Hub.
Preview the intended direction
Choose a trusted client copy for Hub, or use Hub settings in the named client. Read that single server’s preview before confirming.
Verify connection separately
Restart the affected client and test the connection. Successful tool discovery does not prove every backend permission or operation works.
Before you start
Can Hub automatically pick the newest configuration?
A timestamp or equal server name is not enough to decide scope or trust. Real differences need a deliberate choice; automatic bidirectional reconciliation of every MCP edit is not provided.
Can I apply an old preview after changing the config?
No. Rebuild the preview after edits. Reviewed revisions protect against applying a plan to inputs that have changed since inspection.
Start with the one server causing confusion.
The MCP sharing guide explains per-server directions, existing launchers, connection testing and recovery.
See the steps ↗