I am seeing this same issue, but even after promoting a separate account to admin and re-adding the connector, that account still cannot access the MCP server. Only requests from the original admin that added the connector make it through to the server. No other requests from owners or admins make it through, even though they were able to successfully authenticate and add the connector. The docs indicate that once it has been published the rest of the workspace members should be able to use it. I have to assume that is the intent and this is a bug, or what is the point of allowing the connection but not use of the endpoint? My only workaround in the meantime will be to promote each user to admin and have them individually add the connector as a separate new one and this is really not ideal.