What about using Multiple Clients?
how well does this work with multiple clients? we still have to reconnect a million times right?
I have a lot of notes on that, I'll just bullet them.
- Disconnect and reconnect is actually quite smooth through the Claude connector, so the friction here is hugely reduced.
- If your projects are all in one workspace, you can probably do full-workspace auth. I ran into performance issues there maybe 6 mo ago and haven't really retried, but whole-workspace auth is likely smooth and performant again. Multi-workspace auth, yes, disconnect and reconnect.
- If you're still using the local stdio connect, you can probably change it much more easily. I created a wfmcp CLI where I just run it, and it reauths and replaces the existing tokens. Instant inflight changes. And it can override auth at the folder level as well, so for code projects, I'd just go into that local folder, and Claude Code automatically knew its Webflow MCP auth permissions for that project. I didn't release that officially because the connector came out and made my life easier, but happy to if it still benefits anyone.
- Another area I haven't explored is MCP gateways, which is a growing area. You create several auth tokens at the gateway level, and name them. Then you can change configs on the fly for all of your MCP connectors.
Keep me posted if you try stuff, yes this is still a point of scaling MCP access in multi-workspace environments.
