Description
Hi there,
great tool you wrote here. I really like it's idea. I don't know if there is a actual roadmap, but if so, maybe you can consider adding user specific MCP server or actually credentials for the connected MCP servers.
Lets say we have Anna and Bob and both want to use MetaMCP to enable their MCP clients, which don't support OAuth, to access MCP servers that need OAuth to be used.
Anna adds Atlassians MCP server for Jira and Confluence and enters her Bearer token, configures the tools, that should be available to her and thats it.
Bob heard of what she did and wants to use MetaMCP as well. Currently, he would be able to use Annas Atlassian account, as all MCP servers incl. their configs and credentials are shared among the users.
I think it would be really good, if each user can manage their own credentials and have them secure, so nobody can impersonate them.
Maybe you consider that as useful as I do, because from what I've seen so far, this is the cleanest and well structured MCP manager I've seen.