Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@UluVoiMCPWhat is the purpose of Voi application 29090?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ulu-voi-mcp
Voi ecosystem MCP server. Returns meaning, not raw chain data.
Architecture
UluCoreMCP → chain primitives (blocks, accounts, transactions)
UluVoiMCP → Voi ecosystem meaning (protocols, identity, naming)
UluWalletMCP → signing
UluBroadcastMCP → broadcastingCore returns facts. Voi returns meaning.
Tools
Tool | Description |
| List all known Voi protocols, optionally filtered by type |
| Get detailed info about a specific protocol |
| List all contracts and assets for a protocol |
| Human-readable protocol summary |
| Identify what a Voi application ID is |
| Identify what a Voi asset ID is |
| Get the role and purpose of a contract |
| Resolve an enVoi name from static registry |
| Reverse-resolve an address to known names |
| Search the name registry by pattern |
Data Model
Curated registry files in data/:
protocols.json— protocol definitions (HumbleSwap, Nomadex, enVoi, Aramid, etc.)applications.json— application ID → protocol, role, type mappingassets.json— asset ID → name, symbol, category, protocol mappingnames.json— static well-known enVoi names
All registries are static JSON loaded at startup. For live data, use UluCoreMCP.
Setup
npm installUsage
node index.jsClient Configuration
{
"mcpServers": {
"ulu-voi-mcp": {
"command": "node",
"args": ["/absolute/path/to/ulu-voi-mcp/index.js"]
}
}
}Protocols Covered
HumbleSwap — DEX (AMM pools)
Nomadex — DEX
SnowballSwap — DEX aggregator
enVoi — naming service
Nautilus — NFT marketplace
HighForge — NFT minting
Aramid Bridge — cross-chain bridge
Kibisis — browser wallet
Voi Network — L1 blockchain
Naming Resolution
Static registry approach. The names.json file contains well-known enVoi names. For live resolution (on-chain lookups), use UluCoreMCP's envoi_resolve_address, envoi_resolve_name, and envoi_search tools.
Limitations
Registries are static and curated — not all applications or assets are covered
Name resolution is from a static registry, not live on-chain lookups
No write operations — this is a read-only meaning layer
Pool list may become stale as new pools are created
Community tokens marked unverified may change status
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.