{"version":"2.1.248","anchor":"mcp-client-and-auth-modules-resolved-through-dynamic-require","canonical_anchor":"mcp-client-and-auth-modules-resolved-through-dynamic-require","heading":"MCP client and auth modules resolved through dynamic requires","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-client-and-auth-modules-resolved-through-dynamic-require","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP client and auth modules resolved through dynamic requires\n\nThe MCP client and login entry points are now loaded and cached differently at runtime.\n\n**What**\n\nThe MCP client is now built and cached locally rather than fetched from a lazily initialised module, its shutdown clears that cache, and the authentication and identity-provider login entry points are reached through runtime chunk requires.\n\n**Evidence**\n\n`mcpXaaIdpLoginModule()`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}