# What does the MetaMask Connect EVM SDK actually do when the extension is installed?

**URL:** <https://builder.metamask.io/t/what-does-the-metamask-connect-evm-sdk-actually-do-when-the-extension-is-installed/3128>\
**Category:** MetaMask Connect\
**Tags:** faq\
**Created:** [May 8, 2026, 12:58pm UTC](https://builder.metamask.io/t/what-does-the-metamask-connect-evm-sdk-actually-do-when-the-extension-is-installed/3128 "2026-05-08T12:58:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [May 8, 2026, 12:58pm UTC](https://builder.metamask.io/t/what-does-the-metamask-connect-evm-sdk-actually-do-when-the-extension-is-installed/3128/1 "2026-05-08T12:58:57Z")

</div>

With the default configuration (`ui.preferExtension: true`), the SDK:

1. Discovers MetaMask via [EIP-6963](https://eips.ethereum.org/EIPS/eip-6963) — even when other wallets are also injected.

2. Returns the extension’s EIP-1193 provider through `client.getProvider()`.

3. Skips initialization of MWP / QR / mobile transports.

4. Normalizes session, account, and chain events through the same handlers your mobile/QR users hit.

In other words: same provider you’d get from `window.ethereum`, but discovered

reliably and wrapped in a unified API.