MetaMask Embedded Wallets (Web3Auth) MCP

io.github.Web3AuthPublished by GitHub account Web3Authv2.0.0Updated Oct 24, 2026

Helps AI coding agents integrate MetaMask Embedded Wallets (Web3Auth) SDKs.

The publisher's own server: Web3TV MCP Server

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A remote MCP server that gives AI coding assistants live MetaMask Embedded Wallets (Web3Auth) docs, examples, SDK source and community forum search.

What you can do
Search documentation and example projects, returning page links with snippets and matching examples. Fetch the full content of a documentation page by URL. Retrieve complete source code of Web3Auth integration examples from GitHub. Look up SDK source such as types, interfaces and hooks from open-source repositories. Search or fetch posts from the MetaMask Embedded Wallets community forum.
When to use it
Use it when building or debugging a MetaMask Embedded Wallets (Web3Auth) integration and you want the assistant to work from current docs, real example code and SDK types rather than static text. The README suggests pairing it with the companion skill for architecture and key-derivation guidance.
Requirements
A remote HTTP endpoint at mcp.web3auth.io; no local runtime needed, though stdio-only agents can bridge it with mcp-remote via npx. Network access to the endpoint. The hosted deployment expects a GITHUB_TOKEN because example and SDK lookups hit the GitHub API and the unauthenticated rate limit is low; optional DISCOURSE_API_KEY and DISCOURSE_API_USERNAME enable authenticated forum search.
Before you install
The hosted deployment asks for a GITHUB_TOKEN, a personal access token; scope it narrowly. Optional DISCOURSE_API_KEY and DISCOURSE_API_USERNAME are also credentials. Tools are read-only lookups, but queries and fetched URLs go to a third-party server that in turn calls Algolia, GitHub and the MetaMask builder forum. The README warns that config mistakes can change wallet addresses in production, so review generated plans before applying code.

Installation

In SourceWeft

  1. Open MetaMask Embedded Wallets (Web3Auth) MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Web3Auth%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "metamask-embedded-wallets-web3auth": {
      "type": "http",
      "url": "https://mcp.web3auth.io/"
    }
  }
}

README

MetaMask Embedded Wallets MCP Server

Build MetaMask Embedded Wallets integrations faster by giving your AI coding assistant live access to the documentation and deep knowledge of the SDK.

There are two things to set up:

  1. Skill — Teaches your AI assistant how to think about the SDK: architecture, framework quirks, key derivation rules, and common mistakes. No code in the skill; the MCP provides that.
  2. MCP server — Gives your AI assistant real-time access to search docs, fetch examples, and look up SDK types.

MCP Tools

ToolWhat it does
search_docsSearch documentation and example projects
get_docFetch the full content of any doc page
get_exampleFetch complete source code of an integration example
get_sdk_referenceFetch SDK types and hooks from the open-source repos
search_communitySearch the MetaMask Builder Hub for real user issues

Skill

The skill teaches your AI assistant the mental model for MetaMask Embedded Wallets. It includes SDK selection logic, key derivation rules, authentication concepts, platform quirks, and common mistakes that aren't obvious from the docs alone.

Tip: For the best experience, use the MCP server alongside the skill so that your LLM can fetch live docs and examples rather than relying on static text.

Universal install (works with 40+ agents)

bash
npx skills add web3auth/skill

The skills CLI by Vercel detects your active AI agent and installs to the right directory automatically — Cursor, Claude Code, Copilot, Kiro, Cline, Codex, Antigravity, and 40+ more.

To install for target a specific agent:

bash
npx skills add web3auth/skill -a cursor     # Cursor onlynpx skills add web3auth/skill -a claude-code # Claude Code only

MCP Server Setup

Cursor

The fastest way is one click:

[Add MetaMask Embedded Wallets MCP to Cursor]

Or install via Cursor Marketplace — search "MetaMask Embedded Wallets".

Or add it manually. Open Cursor Settings → Tools & Integrations → MCP and add:

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io"    }  }}

VS Code (GitHub Copilot)

Install from the Visual Studio Marketplace — search "MetaMask Embedded Wallets", or:

bash
code --install-extension Web3Auth.metamask-embedded-wallets

Or use the one-click install URL:

vscode:mcp/install?{"name":"web3auth","url":"https://mcp.web3auth.io"}

Or add manually to your workspace .vscode/mcp.json:

json
{  "servers": {    "web3auth": {      "type": "http",      "url": "https://mcp.web3auth.io"    }  }}

JetBrains (IntelliJ, PyCharm, WebStorm, Android Studio)

Install from the JetBrains Marketplace — search "MetaMask Embedded Wallets".

Or add manually in Settings → Tools → AI Assistant → Model Context Protocol (MCP):

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io",      "transport": "http"    }  }}

Claude Code CLI

bash
claude mcp add --transport http web3auth https://mcp.web3auth.io

Or add manually to your project's claude.json:

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io"    }  }}

Claude Desktop

Open your Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the server to the mcpServers section:

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io"    }  }}

Restart Claude Desktop and ask: "Search MetaMask Embedded Wallets docs for React quick start" to verify the connection.

ChatGPT Desktop

Open ChatGPT Desktop → Settings → Connections and add a new MCP server:

  • Name: web3auth
  • URL: https://mcp.web3auth.io

Windsurf

Open Windsurf Settings → MCP and add:

json
{  "mcpServers": {    "web3auth": {      "serverUrl": "https://mcp.web3auth.io"    }  }}

Or edit ~/.codeium/windsurf/mcp_config.json directly.

Kiro (AWS)

Add to your project's .kiro/settings/mcp.json:

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io"    }  }}

Warp Terminal

In Warp, open Settings → AI → MCP Servers and click Add Server:

  • Name: web3auth
  • URL: https://mcp.web3auth.io

Or use Warp's one-click MCP install if available in your version.

Cline (VS Code)

Add to your Cline MCP settings (Ctrl+Shift+P → "Cline: Open MCP Settings"):

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io",      "transport": "http"    }  }}

Continue.dev

Add to your Continue config.json (open with Ctrl+Shift+P → "Continue: Open config.json"):

json
{  "mcpServers": [    {      "name": "web3auth",      "url": "https://mcp.web3auth.io"    }  ]}

Zed

Add to your Zed settings.json (Cmd+, to open):

json
{  "context_servers": {    "web3auth": {      "command": {        "path": "npx",        "args": ["-y", "mcp-remote", "https://mcp.web3auth.io"]      }    }  }}

Or install via Zed Extensions — search "MetaMask Embedded Wallets".

Antigravity

Open your MCP configuration file:

  • macOS/Linux: ~/.config/antigravity/mcp.json
  • Windows: %APPDATA%\antigravity\mcp.json

Add the server to the mcpServers section:

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io"    }  }}

Antigravity hot-reloads MCP config changes — no restart required.

Xcode (via GitHub Copilot)

Xcode 26.3+ supports MCP via GitHub Copilot. Add the server to your Copilot MCP config or use the VS Code extension setup above (Copilot MCP registry is shared).

Alternatively, configure Xcode's agentic tools to point at https://mcp.web3auth.io directly via Settings → Copilot → MCP Servers.

Eclipse (via GitHub Copilot)

Eclipse with GitHub Copilot supports MCP. Add via Eclipse → Preferences → GitHub Copilot → MCP Servers → Add Server:

  • Name: web3auth
  • URL: https://mcp.web3auth.io

Neovim (avante.nvim)

In your Lua config, add via mcphub.nvim:

lua
require("mcphub").setup({  servers = {    web3auth = {      url = "https://mcp.web3auth.io",      transport = "streamable-http",    },  },})

Or using mcp-remote for compatibility:

lua
require("avante").setup({  mcp = {    servers = {      web3auth = {        command = "npx",        args = { "-y", "mcp-remote", "https://mcp.web3auth.io" },      },    },  },})

Neovim (codecompanion.nvim)

lua
require("codecompanion").setup({  extensions = {    mcp = {      servers = {        web3auth = {          command = "npx",          args = { "-y", "mcp-remote", "https://mcp.web3auth.io" },        },      },    },  },})

Amp (Sourcegraph)

Add to your Amp MCP configuration:

json
{  "mcpServers": {    "web3auth": {      "url": "https://mcp.web3auth.io"    }  }}

Goose

Add to ~/.config/goose/config.yaml:

yaml
extensions:  - name: web3auth    type: http    url: https://mcp.web3auth.io

5ire

In 5ire Settings → MCP Servers → Add:

  • Name: web3auth
  • URL: https://mcp.web3auth.io

Aider

Aider supports MCP via the LiteLLM bridge. Add to your Aider config:

yaml
mcp_servers:  web3auth:    command: npx    args: ["-y", "mcp-remote", "https://mcp.web3auth.io"]

Codex CLI

For Codex CLI or any stdio-only agent, use mcp-remote to bridge the HTTP endpoint:

bash
npm install -g mcp-remote

Then add to ~/.codex/config.toml:

toml
[mcp_servers.web3auth]command = "npx"args = ["-y", "mcp-remote", "https://mcp.web3auth.io"]

Or add to your agent's JSON config:

json
{  "mcpServers": {    "web3auth": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.web3auth.io"]    }  }}

Static docs (llms.txt)

If your AI tool doesn't support MCP yet, use the static documentation file instead:

https://docs.metamask.io/llms-full.txt

For tools that support the llms.txt spec and can index docs automatically:

https://docs.metamask.io/llms.txt

Warning: The static file is a snapshot and may not include the latest updates. Use the MCP server when possible for always-current docs.


Start building

Once the skill and MCP are set up, ask your AI assistant directly. Good starting prompts:

  • "Add MetaMask Embedded Wallets to my React app with Google login."
  • "Set up social login wallets in my Next.js app using Wagmi."
  • "Integrate embedded wallets in my Flutter app."
  • "Why are my users getting different wallet addresses after I changed the login method?"

Tip: Use planning mode (where available) for your initial prompt. Review the plan before generating code — this catches architecture mistakes early and avoids config errors that would change wallet addresses in production.


Distribution

This repo ships artifacts for every major developer platform:

PlatformTypeLocation
Cursor MarketplacePlugin.cursor-plugin/ + mcp.json
VS Code MarketplaceExtensionplugins/vscode/
JetBrains MarketplacePluginplugins/jetbrains/
Zed ExtensionsExtensionplugins/zed/
Claude Agent SDKPluginplugins/claude/
Raycast StoreExtensionplugins/raycast/
ChatGPT GPT StoreCustom GPTopenai/
Official MCP Registryserver.jsonserver.json
Glamaglama.jsonglama.json
SmitheryServer cardapp/.well-known/mcp/server-card.json/route.ts
Vercel skills.shSkillWeb3Auth/skill
agentskill.shSkillWeb3Auth/skill

Environment Variables

VariableRequiredDescription
GITHUB_TOKENYes (hosted) / recommended (local)GitHub personal access token. Required on the Vercel deployment (mcp.web3auth.io) — get_example and get_sdk_reference call the GitHub API heavily; without a token the shared IP hits the 60 req/hr unauthenticated limit quickly. Optional for local stdio use.
DISCOURSE_API_KEYNoDiscourse API key for search_community (optional; public search works without it)
DISCOURSE_API_USERNAMENoDiscourse API username when using DISCOURSE_API_KEY

Development

bash
npm installnpm run buildnpm test           # Handler smoke tests (mocked fetch)npm start          # Run via stdionpm run dev        # Watch mode

Updating Content

What changedWhere to update
SDK architecture, platform quirks, key derivation, workflowWeb3Auth/skill (SKILL.md)
New example repository or scan root (e.g. new platform)src/content/example-catalog.ts
New SDK repository or discovery rules (e.g. new platform)src/content/sdk-catalog.ts
New tool or parameter changessrc/tools/register.ts
Example folders / SDK file layout within existing reposNothing (discovered live from GitHub, cached 4h)
Doc page contentNothing (fetched live via Algolia / llms.txt / GitHub)

License

MIT

Source: README.md at commit 58eec17

Tools

5

search_docs

Search MetaMask Embedded Wallets documentation (Algolia) and example projects. Returns doc page links with snippets and matching examples.

Parameterschainqueryrequiredcategoryplatform

get_doc

Fetch the full content of a MetaMask Embedded Wallets documentation page by URL. Sources: Algolia, llms.txt, GitHub MDX.

Parametersurlrequired

get_example

Fetch complete source code of a Web3Auth integration example from GitHub.

Parametersnamechaincategoryplatformauth_method

get_sdk_reference

Fetch SDK source code (types, interfaces, hooks) from open-source Web3Auth repos.

Parametersfocusmoduleplatformrequired

search_community

Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io).

Parametersquerytopic_id

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Web3 integrations