In the world of protected MCP servers, and especially those that do follow the authorization specification, the MCP servers themselves need to either rely on Authorization Servers (referred to as AS) that support Dynamic Client Registration (DCR) to make the MCP client-to-server interactions work. In this process, the user of the MCP client is, in fact, redirected to the authorization page from the downstream AS, however the token is returned to the MCP server and not the MCP client directly. Mini MCP Server then redirects the authorization request to Entra ID, with its static client ID (not the same as the freshly-issued DCR client ID for Awesome MCP Client).