MetaMask Embedded Wallets MCP

MetaMask Embedded Wallets MCP (formerly Web3Auth) gives AI coding assistants live access to Embedded Wallets documentation, SDK references, integration…

CommunityRequires local installNo sign-inGlobalFreeRead-only
This server only runs on your computer. It cannot be added to Claude or ChatGPT web. See the project docs for installation.

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    MetaMask Embedded Wallets MCP (formerly Web3Auth) gives AI coding assistants live access to Embedded Wallets documentation, SDK references, integration examples, and community troubleshooting. MetaMask Embedded Wallets is not a wallet app itself, but embedded wallet infrastructure that helps developers add non-custodial Web3 wallets to web, mobile, and gaming apps using familiar login methods like Google, GitHub, email, SMS, and other OAuth or passwordless flows.

    This MCP server is built for real integration work. It lets agents search docs, fetch full documentation pages, retrieve complete example code, inspect SDK types and hooks, and surface real-world implementation issues. It is especially useful for tasks like choosing the right SDK, implementing social login, understanding key derivation behavior, avoiding wallet address changes caused by auth or configuration mistakes, and debugging framework-specific issues across React, Next.js, Flutter, React Native, and other platforms.

    U

    Requires a local install: run the server on your machine, then point your client at it.

    How to connect

    How to connect MetaMask Embedded Wallets MCP to Claude

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect MetaMask Embedded Wallets MCP to ChatGPT

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect MetaMask Embedded Wallets MCP to Cursor

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    Server tool list (5)

    Raw names from tools/list. Only developers need these.

    search_docsSearch MetaMask Embedded Wallets (Web3Auth) documentation and examples. Use for SDK discovery, feature lookup, and finding relevant examples. Returns doc page links with snippets and matching example projects.
    get_docFetch the full content of a MetaMask Embedded Wallets documentation page. Use after search_docs to read the actual doc. Tries Algolia, then llms.txt, then GitHub raw MDX as fallbacks.
    get_exampleFetch the complete source code of a Web3Auth integration example from GitHub. Returns all source files needed to understand how the integration works. Examples are the PRIMARY reference for integration patterns — always prefer example code over raw SDK source.
    get_sdk_referenceFetch SDK source code (type definitions, interfaces, hooks) from the open-source Web3Auth SDK repos. Use for REFERENCE and DEBUGGING only — to verify exact type shapes, constructor signatures, available hooks, and error types. Do NOT use this to discover features; many SDK options are internal or legacy. Always use get_example first for integration patterns.
    search_communitySearch or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). Use for troubleshooting real user issues, finding workarounds, and checking if an issue is known. Provide a query to search or a topic_id to read the full discussion.