Remote MCP servers with OAuth

Connect a remote MCP server over HTTPS and authenticate the client with OAuth. The authorization flow issues a scoped token the client presents to the protected endpoint, letting the server enforce what the client may do.

The client starts an OAuth flow at the server, the user approves within the requested scopes, and the client receives an access token. Subsequent requests carry the token to the protected MCP endpoint.

Only protected capabilities require tokens. A server advertises which endpoints and capabilities need authorization, and enforces the granted scopes on each request.