MultiversX MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set logging level (DEBUG, INFO, WARN, ERROR) | |
| MULTIVERSX_NETWORK | No | Default network (mainnet, testnet, devnet) |
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 | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mx-query-accountB | Query MultiversX account information including balance, nonce, transactions, and guardian status for any network (mainnet, testnet, devnet) |
| mx-sdk-dapp-guideA | Fetch the MultiversX SDK-DAPP v5 guide, including setup and usage for React, TypeScript, JavaScript, Angular, login/logout, signing, sending, tracking transactions, signing messages, and creating custom providers. Optionally, provide a section name to extract a specific section. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SDK-DAPP v5 Complete Guide | Comprehensive guide for SDK-DAPP v5 usage, initialization, and best practices |
TDQS
Scored across 2 tools
The two tools serve completely distinct purposes: one queries live on-chain account data, the other retrieves static SDK documentation. There is no realistic scenario where an agent would confuse them.
Both names share a consistent 'mx-' prefix and kebab-case formatting, which is predictable. The main deviation is that one uses an action verb (query) while the other is a noun-style resource name (sdk-dapp-guide).
Two tools is thin for a server branded as a general MultiversX blockchain interface. The scope implied by the name suggests querying blocks, tokens, NFTs, and submitting transactions, so the surface feels under-developed rather than intentionally minimal.
The surface only supports reading a single account; there are no tools for tokens, NFTs, blocks, smart contracts, or sending transactions. This leaves significant gaps for anything beyond read-only account inspection, though the doc tool partially compensates by describing transaction workflows.