Datai MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3099 |
| DEBUG | No | Enable debug logging | false |
| NODE_ENV | No | Node environment configuration | |
| DATAI_LIMIT | No | API response limit (1-100) | 10 |
| DATAI_API_KEY | Yes | Your Datai API key | |
| MCP_DISABLE_PINGS | No | Option to disable MCP pings | |
| DATAI_DEBUG_TRUNCATE | No | Enable data truncation for debugging | false |
| DATAI_RESPONSE_TIMEOUT | No | Response timeout in ms | 90000 |
| DATAI_CONNECTION_TIMEOUT | No | Connection timeout in ms | 130000 |
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 | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_defi_positionsA | Get comprehensive DeFi positions for a wallet across ALL supported blockchain networks and protocols. Provides complete portfolio overview including lending, liquidity pools, yield farming, staking, and other DeFi activities across 10+ chains and 15+ protocols. |
| get_defi_by_chainA | Get DeFi positions for a wallet on a specific blockchain network. Provides detailed information about lending, liquidity pools, yield farming, and other DeFi activities on the specified chain. |
| get_defi_multi_chainsA | Get DeFi positions for a wallet across multiple specified blockchain networks. Allows targeted multi-chain analysis by selecting specific chains of interest for comparison and portfolio analysis. |
| get_defi_by_protocolA | Get DeFi positions for a wallet filtered by a specific protocol across all chains. Provides detailed analysis of exposure to a particular DeFi protocol for risk assessment and yield optimization. |
| get_defi_balances_by_chainA | Get DeFi protocol balances for a wallet on a specific blockchain network. Provides aggregated balance information grouped by protocol for diversification analysis and risk assessment. |
| get_overall_balance_all_cA | Get overall balance for a wallet across ALL supported blockchain networks in multiple currencies. Provides complete portfolio valuation including USD, EUR, AUD, and other major currencies for comprehensive wealth tracking. |
| get_overall_balance_by_chainA | Get comprehensive overall balance for a wallet on a specific blockchain network in multiple currencies (USD, EUR, AUD, GBP, JPY, CAD, CHF). Provides aggregated portfolio valuation across all assets held on the specified chain. |
| get_wallet_balances_by_chainA | Get token balances for a wallet on a specific blockchain network. Provides detailed information about all token holdings including amounts, USD values, and token metadata for portfolio analysis. |
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 8 tools
Multiple tools have unclear boundaries and overlapping purposes, causing potential confusion. For example, 'get_defi_balances_by_chain' and 'get_wallet_balances_by_chain' both retrieve balances on a specific chain, while 'get_defi_by_chain' and 'get_defi_multi_chains' overlap in multi-chain analysis. The descriptions help somewhat, but the distinctions are not clearly defined.
The naming follows a mostly consistent verb_noun pattern with 'get_' prefix throughout, making tools readable and predictable. However, there are minor deviations like 'get_all_defi_positions' (adjective before noun) and 'get_overall_balance_all_c' (abbreviated 'all_c'), which slightly break the pattern but do not severely impact usability.
With 8 tools, the count is reasonable for a DeFi portfolio analysis server, but it feels borderline due to the significant overlap and redundancy among tools. The server could benefit from consolidation, as some tools (e.g., 'get_defi_by_chain' and 'get_defi_multi_chains') serve similar purposes, making the set feel slightly heavy for its scope.
The tool surface covers the domain of DeFi and wallet portfolio analysis well, with tools for overall balances, DeFi positions, and chain/protocol-specific queries. Minor gaps exist, such as no tools for historical data or transaction analysis, but agents can work around these for core tasks like portfolio overview and risk assessment.