Description
First off, thanks for this great tool – I've been using it for about 3 weeks to centralize my MCP server management across different IDEs (like Cursor, Winsurf, Trae), and it's been a big help!
I wanted to share some thoughts on the "Workplace" and "Project" features. I was completely lost on how to use them until I saw our chats on Discord. Even now that I understand them, I find them really confusing and not super practical for my workflow. Here's my take:
- Projects: Currently, a Project lets you enable or disable specific MCP servers. However, you can only have one Project active at a time. This makes it tricky if I want to work on two different coding projects simultaneously, as I can't use different MCP setups for each.
- Workplace: To work on multiple coding projects at once, I need to use Workplace. This lets me have another set of MCPs, but I have to define the servers all over again for each Workplace. The import/export tool helps a bit, but I still end up managing server lists in multiple places, and there any many servers are common (like time, sequential thinking, firecrawl etc...).
So, I'm often left confused when I should use a Project versus a Workplace. For example, if I want one set of MCP servers for coding and another for studying, both approach have negative drawbacks make me don't want to use them.
My Suggestion:
-
What if we simplified things to just one core concept? Whatever we call it, its main purpose would be to let users create groups of servers and, importantly, allow us to use multiple groups at the same time. I think this would cover most everyday needs and be much more straightforward.
-
I've also suggested Feature: Expose MCP endpoint for a single server by its name or ID #43. In the worst-case scenario, I can still add a separate server for each client.
Thanks for listening!