As this feature was released today, I must point out that what was delivered missed the entire point of this feature request. I can add a shared Custom MCP that uses a shared API key, however I cannot add a custom MCP that uses OAuth so that each user needs to auth to use it the first time. Providing users instructions to add a custom MCP when 100% of the users are going to have to do it is a poor experience and a blocker to sales/success. Yet another

"I can do this in Claude" situation.

Let Hatz admins decide if the MCP connection is to have its authentication shared as well (basic token or API) or if it should be an oAuth user level authentication process to the Hatz user as part of the sharing ability.

This is quickly becoming a need very quickly. Clients want this functionality and it would stop the conversation about other platforms.

I'm about to implement an MCP that accesses a custom CRM. Having it share company wide would be a huge help so we don't have to expose the authentication key to everyone.