Skip to main content

MetaMask Connect EVM methods

MetaMask Connect EVM (@metamask/connect-evm) exposes several methods, including:

createEVMClient

Creates a new EVM client instance.

Parameters

NameTypeRequiredDescription
dapp.namestringYesName of your dapp.
dapp.urlstringNoURL of your dapp. In browsers this is often set automatically; required in Node.js and React Native.
dapp.iconUrlstringNoURL of your dapp icon.
dapp.base64IconstringNoBase64-encoded icon when a hosted URL is unavailable (for example, some React Native setups). Use instead of iconUrl when needed.
api.supportedNetworksRecord<string, string>NoMap of hex chain IDs to RPC URLs for read-only requests and transport. Use getInfuraRpcUrls to generate Infura URLs, then merge custom endpoints.
ui.headlessbooleanNoEnables or disables headless mode. The default is false.
ui.preferExtensionbooleanNoDirectly connects through the MetaMask extension when it's installed. The default is true.
mobile.preferredOpenLink(deeplink: string) => voidNoA function that's called to open a deeplink to the MetaMask Mobile App. Required in React Native.
mobile.useDeeplinkbooleanNoControls use of deeplinks for mobile connection flows.
eventHandlersobjectNoOptional callbacks for connection lifecycle and provider events.

Returns

Returns a promise that resolves to an EVM client instance. The client is a singleton; calling createEVMClient again returns the same instance.

Example

import { createEVMClient, getInfuraRpcUrls } from '@metamask/connect-evm'

const evmClient = await createEVMClient({
dapp: {
name: 'My Dapp',
url: window.location.href,
iconUrl: 'https://mydapp.com/icon.png',
},
api: {
supportedNetworks: {
...getInfuraRpcUrls({ infuraApiKey: process.env.INFURA_API_KEY }),
'0x89': 'https://polygon-rpc.com',
},
},
ui: {
headless: false,
preferExtension: true,
},
mobile: {
preferredOpenLink: link => window.open(link, '_blank'),
},
})

connect

Connects to MetaMask and requests account access.

Parameters

NameTypeRequiredDescription
options.chainIdsHex[]NoArray of hex chain IDs to request permission for (defaults to ['0x1'] if not provided). Ethereum Mainnet (0x1) is always included in the request regardless of what is passed.
options.accountstringNoSpecific account address to connect.
options.forceRequestbooleanNoForce a new connection request even if already connected.

Returns

A promise that resolves to an object containing accounts (an array of account addresses) and chainId.

Example

const { accounts, chainId } = await evmClient.connect({
chainIds: ['0x1', '0x89'],
})
console.log('Connected accounts:', accounts)

connectAndSign

Connects to MetaMask and signs a personal_sign message in a single user approval.

Parameters

NameTypeRequiredDescription
options.messagestringYesThe message to sign.
options.chainIdsHex[]NoArray of hex chain IDs to request permission for (defaults to ['0x1']).

Returns

A promise that resolves to an object with the following fields:

FieldTypeDescription
accountsAddress[]The accounts permitted on the resulting session.
chainIdHexThe selected chain ID as a hex string.
signaturestringThe personal_sign signature as a hex string.
Breaking change in @metamask/connect-evm 1.0.0

connectAndSign previously returned the signature as a bare string. It now returns { accounts, chainId, signature }. Read .signature from the returned object to get the signed value.

tip

You can also subscribe to the connectAndSign event handler when initializing the client with createEVMClient to receive the same payload:

eventHandlers: {
connectAndSign: ({ accounts, chainId, signature }) => {
console.log('Accounts:', accounts, 'Chain:', chainId, 'Signature:', signature)
},
}

Example

const { accounts, chainId, signature } = await evmClient.connectAndSign({
message: 'Sign in to My Dapp',
chainIds: ['0x1'],
})
console.log('Accounts:', accounts, 'Chain:', chainId, 'Signature:', signature)

connectWith

Connects to MetaMask and executes a specific JSON-RPC method in a single user approval.

Parameters

NameTypeRequiredDescription
options.methodstringYesThe JSON-RPC method name.
options.paramsunknown[] | (account: Address) => unknown[]YesThe parameters for the method. Can be a function that receives the connected account and returns params.
options.chainIdsHex[]NoArray of hex chain IDs to request permission for (defaults to ['0x1']).
options.accountstringNoSpecific account address to connect.
options.forceRequestbooleanNoForce a new connection request even if already connected.

Returns

A promise that resolves to an object with the following fields:

FieldTypeDescription
accountsAddress[]The accounts permitted on the resulting session.
chainIdHexThe selected chain ID as a hex string.
resultunknownThe result of the JSON-RPC method invocation.
Breaking change in @metamask/connect-evm 1.0.0

connectWith previously returned the raw RPC result. It now returns { accounts, chainId, result }. Read .result from the returned object to get the RPC response value.

tip

You can also subscribe to the connectWith event handler when initializing the client with createEVMClient to receive the same payload:

eventHandlers: {
connectWith: ({ accounts, chainId, result }) => {
console.log('Accounts:', accounts, 'Chain:', chainId, 'Result:', result)
},
}

Example

const {
accounts,
chainId,
result: txHash,
} = await evmClient.connectWith({
method: 'eth_sendTransaction',
params: account => [
{
from: account,
to: '0xRecipientAddress',
value: '0x2386F26FC10000',
},
],
chainIds: ['0x1'],
})
console.log('Accounts:', accounts, 'Chain:', chainId, 'Transaction hash:', txHash)

switchChain

Switches the active chain on the EVM client. If the chain is not already added to the user's MetaMask wallet, the optional chainConfiguration parameter triggers a wallet_addEthereumChain request as a fallback.

Parameters

NameTypeRequiredDescription
options.chainIdHexYesThe hex chain ID to switch to.
options.chainConfigurationobjectNoFallback chain details if the chain is not yet added to MetaMask.
options.chainConfiguration.chainNamestringYesHuman-readable chain name.
options.chainConfiguration.nativeCurrencyobjectYes{ name, symbol, decimals } for the native token.
options.chainConfiguration.rpcUrlsstring[]YesArray of RPC endpoint URLs.
options.chainConfiguration.blockExplorerUrlsstring[]NoArray of block explorer URLs.

Example

await evmClient.switchChain({
chainId: '0xa4b1',
chainConfiguration: {
chainName: 'Arbitrum One',
nativeCurrency: { name: 'Ether', symbol: 'ETH', decimals: 18 },
rpcUrls: ['https://arb1.arbitrum.io/rpc'],
blockExplorerUrls: ['https://arbiscan.io'],
},
})

getProvider

Returns the active EIP-1193 Ethereum provider object. The provider is available immediately after createEVMClient resolves, even before calling connect. Read-only RPC calls work immediately; account-dependent calls require connect first.

Returns

An EIP-1193 compatible provider object.

Example

const provider = evmClient.getProvider()
const chainId = await provider.request({ method: 'eth_chainId' })
console.log('Current chain:', chainId)

getChainId

Returns the currently selected chain ID.

Returns

Hex | undefined - The currently selected chain ID as a hex string, or undefined if not connected.

Example

const chainId = evmClient.getChainId()
console.log('Current chain:', chainId) // e.g., '0x1'

getAccount

Returns the currently selected account.

Returns

Address | undefined - The currently selected account address, or undefined if not connected.

Example

const account = evmClient.getAccount()
console.log('Current account:', account) // e.g., '0x...'

disconnect

Disconnects all EVM (eip155) scopes from MetaMask and cleans up local state. This only revokes the EVM-specific scopes currently held in the session; it does not terminate the broader multichain session if non-EVM scopes (such as Solana) are also active.

Multichain partial disconnect

If your dapp also uses Solana via the multichain client, calling disconnect on the EVM client only revokes EVM (eip155) scopes. Non-EVM scopes remain active, so the user stays connected to Solana.

Example

await evmClient.disconnect()

getInfuraRpcUrls

Generates a map of Infura RPC URLs keyed by hex chain ID. Use this utility to populate api.supportedNetworks when calling createEVMClient.

note

Each chain must be activated in your Infura dashboard before getInfuraRpcUrls can generate working URLs for it.

Parameters

NameTypeRequiredDescription
infuraApiKeystringYesYour Infura API key.
chainIdsstring[]NoArray of hex chain IDs to include (for example, ['0x1', '0x89']). If omitted, all supported chains are included.

Returns

A Record<string, string> mapping hex chain IDs to Infura RPC URLs. When chainIds is provided, only matching chains are included.

Example

import { createEVMClient, getInfuraRpcUrls } from '@metamask/connect-evm'

const evmClient = await createEVMClient({
dapp: { name: 'My Dapp', url: window.location.href },
api: {
supportedNetworks: {
// Each chain must be active in your Infura dashboard
...getInfuraRpcUrls({ infuraApiKey: 'YOUR_INFURA_API_KEY', chainIds: ['0x1', '0xaa36a7'] }),
},
},
})

Properties

The EVM client exposes the following read-only properties:

PropertyTypeDescription
accountsAddress[]Currently permitted accounts.
selectedAccountAddress | undefinedCurrently selected account (first in accounts).
selectedChainIdHex | undefinedCurrently selected chain ID as a hex string.
statusConnectEvmStatusConnection status: 'loaded', 'pending', 'connecting', 'connected', or 'disconnected'.

Example

console.log('Status:', evmClient.status)
console.log('Accounts:', evmClient.accounts)
console.log('Selected account:', evmClient.selectedAccount)
console.log('Selected chain:', evmClient.selectedChainId)