Looks like this is possible due to the relatively recent addition of OAuth2.1 to the MCP spec [0] to allow secure comms to remote servers. However, there's a major concern that server hosters are on the hook to implement authorization. Ongoing discussion here [1]. [0] https://modelcontextprotocol.io/specification/2025-03-26 [1] https://github.com/modelcontextprotocol/modelcontextprotocol...
> major concern that server hosters are on the hook to implement authorization
Doesn't it make perfect sense for server hosters to implement that? If Claude wants access to my Jira instance on my behalf, and Jira hosts a remote MCP server that aids in exposing the resources I own, isn't it obvious Jira should be responsible for authorization?
How else would they do it?