web3auth
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token. Required for hosted deployment (mcp.web3auth.io) to avoid hitting unauthenticated rate limits; recommended for local use. | |
| DISCOURSE_API_KEY | No | Optional Discourse API key for search_community. Public search works without it. | |
| DISCOURSE_API_USERNAME | No | Optional Discourse API username when using DISCOURSE_API_KEY. |
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 documentation (Algolia) and example projects. Returns doc page links with snippets and matching examples. |
| get_docB | Fetch the full content of a MetaMask Embedded Wallets documentation page by URL. Sources: Algolia, llms.txt, GitHub MDX. |
| get_exampleA | Fetch complete source code of a Web3Auth integration example from GitHub. |
| get_sdk_referenceA | Fetch SDK source code (types, interfaces, hooks) from open-source Web3Auth repos. |
| search_communityA | Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). |
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 distinct purpose: searching docs, fetching doc pages, retrieving examples, fetching SDK source, and searching the community forum. Even the two code-fetching tools are clearly differentiated by target.
All tool names follow a consistent lowercase verb_noun pattern (search_* and get_*). The minor singular/plural variation between get_doc and search_docs is negligible.
Five tools is well-scoped for a documentation and developer-support knowledge server. Each tool fills a clear role without redundancy or bloat.
The tool surface covers the full knowledge workflow: discover via search, read full docs, inspect examples, examine SDK source, and check community discussions. No significant gaps are apparent for this domain.