MetaMask Embedded Wallets MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token. Optional but recommended to avoid rate limits when fetching SDK source code via get_sdk_reference |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search 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_docA | Fetch 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_exampleA | Fetch 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_referenceA | Fetch 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_communityA | Search 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_doc retrieves documentation content, get_example fetches example code, get_sdk_reference provides SDK source for debugging, search_community accesses forum discussions, and search_docs performs initial documentation searches. The descriptions explicitly differentiate their roles and use cases, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case: get_doc, get_example, get_sdk_reference, search_community, and search_docs. This uniformity makes the tool set predictable and easy to understand at a glance.
With 5 tools, the server is well-scoped for its purpose of providing MetaMask Embedded Wallets resources. Each tool serves a specific function (documentation, examples, SDK reference, community, and search), and none feel redundant or missing given the domain of developer support and integration.
The tool set covers key areas for developer integration: documentation access, example code, SDK reference, community support, and search functionality. A minor gap exists in not having tools for direct wallet operations or API interactions, but this is reasonable as the server focuses on resource retrieval rather than live wallet management.