MCPs per user

[matanyaasisinnovid]

I wanted to use this tool but I encounter an issue when multiple developers want to have their own seperated list of MCPs
e.g. Bob wants Mysql and AWS with his creds and Alice wants Postgress and AWS with her own creds
if all of them will register MCPs to the same McpJungle instance in the cloud they both have access to Mysql, Postgress and AWS of each other!
my suggestion - separation by user name/user id so that each user will be exposed only to MCPs register by the user

[duaraghav8]

@matanyaasisinnovid We're currently exploring the ideas of Tool Groups and Namespaces to solve for a use case like yours.

Ideally, would you want that each user (or a group of users) can control a set of MCP servers (like register them and use them) or would you prefer that an administrator manages these different groups?

If the groups are admin-controlled, the users can only call the tools but not control them. On the other hand, if users have the ability to control MCPs, then it is more self-serve.