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:
- 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.
- MCP server — Gives your AI assistant real-time access to search docs, fetch examples, and look up SDK types.
| Tool | What it does |
|---|---|
search_docs |
Search documentation and example projects |
get_doc |
Fetch the full content of any doc page |
get_example |
Fetch complete source code of an integration example |
get_sdk_reference |
Fetch SDK types and hooks from the open-source repos |
search_community |
Search the MetaMask Builder Hub for real user issues |
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.
npx degit Web3Auth/web3auth-mcp/skills/web3auth .cursor/skills/web3authCursor picks up any SKILL.md inside .cursor/skills/ automatically and activates it when relevant.
npx degit Web3Auth/web3auth-mcp/skills/web3auth /tmp/web3auth-skill
cat /tmp/web3auth-skill/SKILL.md >> CLAUDE.mdOpen Claude Desktop → Settings → Custom Instructions and paste the contents of skills/web3auth/SKILL.md directly.
npx degit Web3Auth/web3auth-mcp/skills/web3auth .agent/skills/web3authAntigravity picks up skills inside .agent/skills/ automatically. For global installation across all
projects, use ~/.gemini/antigravity/skills/ instead.
For any LLM tool with a system prompt or custom instructions field, paste the contents of
skills/web3auth/SKILL.md directly.
The fastest way is one click:
Or add it manually. Open Cursor Settings → Tools & Integrations → MCP and add:
{
"mcpServers": {
"web3auth": {
"url": "https://mcp.web3auth.io"
}
}
}claude mcp add --transport http web3auth https://mcp.web3auth.ioOr add manually to your project's claude.json:
{
"mcpServers": {
"web3auth": {
"url": "https://mcp.web3auth.io"
}
}
}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:
{
"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.
Open your MCP configuration file:
- macOS/Linux:
~/.config/antigravity/mcp.json - Windows:
%APPDATA%\antigravity\mcp.json
Add the server to the mcpServers section:
{
"mcpServers": {
"web3auth": {
"url": "https://mcp.web3auth.io"
}
}
}Antigravity hot-reloads MCP config changes — no restart required.
For Codex CLI or any stdio-only agent, use mcp-remote to bridge the HTTP endpoint:
npm install -g mcp-remoteThen add to your agent's configuration:
{
"mcpServers": {
"web3auth": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.web3auth.io"]
}
}
}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.
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.
| Variable | Required | Description |
|---|---|---|
GITHUB_TOKEN |
No | GitHub personal access token. Optional but recommended to avoid rate limits when fetching SDK source code via get_sdk_reference |
npm install
npm run build
npm start # Run via stdio
npm run dev # Watch modeWhen a product update ships, only a few files need changing:
| What changed | File to update |
|---|---|
| SDK architecture / new gotchas | skills/web3auth/SKILL.md |
| New doc pages or URL changes | src/content/registry.ts |
| Platform capabilities changed | src/content/platform-matrix.ts |
| SDK repo structure changed | src/content/sdk-registry.ts |
| New tool category needed | src/tools/register.ts |
| Doc page content changed | Nothing (fetched live) |
MIT