High-performance FastMCP TypeScript server for Datai blockchain data endpoints - NPX Ready
Datai MCP server exists for a simple reason — assistants are far more useful when they can act on Datai directly instead of describing what you should do. High-performance FastMCP TypeScript server for Datai blockchain data endpoints - NPX Ready.
Whether you're building with Eliza OS, Cursor, or any local agent stack — simply plug in a wallet address, and the MCP server delivers clean, real-time context powered by the Datai API.
Datai is building the agentic data layer for Web3. We provide high-quality, real-time data pipelines powering agents, AI copilots, and smart protocols. The Datai MCP is one step in our journey to make wallet data accessible, actionable, and agent-ready.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Datai is connected, these are the calls the assistant has available:
Authentication — API key-basedget_all_defi_positions — Get all DeFi positions across all supported chainsget_defi_by_chain — Get DeFi positions for a specific blockchainget_defi_multi_chains — Get DeFi positions across multiple chainsget_defi_by_protocol — Get DeFi positions for a specific protocolget_defi_balances_by_chain — Get DeFi protocol balances by chainget_overall_balance_all_c — Get overall balance across all chainsget_overall_balance_by_chain — Get overall balance for a specific chainget_wallet_balances_by_chain — Get token balances for a specific chainPrerequisites — The Prerequisites tool exposed by this serverRecommendations — Until summarization and modular querying are available, we recommend: - Using lightweight wallets for testing and debugging - Manually filtering orYou will need 8 environment variables: DATAI_API_KEY, DATAI_LIMIT, DATAI_DEBUG_TRUNCATE, DATAI_CONNECTION_TIMEOUT, DATAI_RESPONSE_TIMEOUT, PORT, DEBUG, MCP_DISABLE_PINGS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Datai's toolset — Authentication, get_all_defi_positions, get_defi_by_chain and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Datai-Network; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Datai's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Authentication | API key-based |
| get_all_defi_positions | Get all DeFi positions across all supported chains |
| get_defi_by_chain | Get DeFi positions for a specific blockchain |
| get_defi_multi_chains | Get DeFi positions across multiple chains |
| get_defi_by_protocol | Get DeFi positions for a specific protocol |
| get_defi_balances_by_chain | Get DeFi protocol balances by chain |
| get_overall_balance_all_c | Get overall balance across all chains |
| get_overall_balance_by_chain | Get overall balance for a specific chain |
| get_wallet_balances_by_chain | Get token balances for a specific chain |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Recommendations | Until summarization and modular querying are available, we recommend: - Using lightweight wallets for testing and debugging - Manually filtering or summarizing MCP responses before injecting into your agent - Keeping res |
{
"mcpServers": {
"datai-fastmcp-server-local": {
"command": "node",
"args": ["/path/to/your/datai-mcp/dist/index.js"],
"env": {
"DATAI_API_KEY": "your_api_key_here",
"DATAI_LIMIT": "1",
"DATAI_DEBUG_TRUNCATE": "true",
"DATAI_CONNECTION_TIMEOUT": "130000",
"DATAI_RESPONSE_TIMEOUT": "90000",
"PORT": "3099",
"DEBUG": "true",
"NODE_ENV": "production",
"MCP_DISABLE_PINGS": "true"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DATAI_API_KEY | Credential the server authenticates with. | Yes |
| DATAI_LIMIT | Configuration value read at startup. | Optional |
| DATAI_DEBUG_TRUNCATE | Configuration value read at startup. | Optional |
| DATAI_CONNECTION_TIMEOUT | Configuration value read at startup. | Optional |
| DATAI_RESPONSE_TIMEOUT | Configuration value read at startup. | Optional |
| PORT | Configuration value read at startup. | Optional |
| DEBUG | Configuration value read at startup. | Optional |
| MCP_DISABLE_PINGS | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.