KAIA-MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAIA_NETWORK | No | Network (only kaia supported currently) | kaia |
| KAIA_RPC_URL | No | KAIA Mainnet RPC URL | https://public-en.node.kaia.io |
| KAIA_AGENT_MODE | No | Agent mode: 'readonly' for safe exploration and data analysis, or 'transaction' for full DeFi operations with transaction capabilities | readonly |
| KAIA_PRIVATE_KEY | No | Wallet private key (required for transaction mode, must be 64 hex characters with or without 0x prefix) |
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 |
|---|---|
| kaia_get_wallet_infoC | Get comprehensive wallet information including all token balances |
| kilolend_get_account_liquidityB | Check account liquidity, health factor, and borrowing capacity on KiloLend |
| kilolend_get_lending_marketsB | Get all lending markets KiloLend with their current rates and statistics |
| kilolend_get_lending_statsA | Get overall KiloLend protocol statistics and TVL information |
| kilolend_get_kilo_pointsB | Get user KILO points balance |
| dragonswap_get_quoteA | Get a quote for swapping tokens on DragonSwap V3 DEX. Note: USDT uses 6 decimals, most other tokens use 18 decimals. For stKAIA, you can use either 'stKAIA' or 'STAKED_KAIA'. |
| dragonswap_get_pool_infoB | Get detailed information about a DragonSwap V3 pool |
| dragonswap_get_routeA | Get the best routing path for swapping tokens (supports multi-hop for better prices) on DragonSwap V3 DEX |
| get_all_pricesA | Get comprehensive market data including prices, market capitalization, 24h trading volume, and 24h price changes for all available tokens from the KiloLend price API (KAIA ecosystem tokens and major cryptocurrencies) |
| get_token_pricesB | Get comprehensive market data including prices, market capitalization, 24h trading volume, and 24h price changes for specific token symbols (e.g., 'KAIA', 'BTC', 'ETH', 'BORA') |
| get_kaia_ecosystem_pricesA | Get comprehensive market data including prices, market capitalization, 24h trading volume, and 24h price changes for KAIA ecosystem tokens only (KAIA, BORA, MBX, SIX, stKAIA) |
| get_major_crypto_pricesB | Get comprehensive market data including prices, market capitalization, 24h trading volume, and 24h price changes for major cryptocurrencies (BTC, ETH) |
| get_quick_pricesA | Get quick comprehensive market overview including prices, market capitalization, 24h trading volume, and 24h price changes for KAIA, BTC, and ETH |
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 13 tools
The price tools (get_all_prices, get_kaia_ecosystem_prices, get_major_crypto_prices, get_quick_prices, get_token_prices) heavily overlap, making it unclear which one to use. The other groups are distinct, but the redundancy in the price category hurts disambiguation.
Naming uses snake_case with prefixes (dragonswap_, kilolend_, kaia_) and a generic 'get_' for price tools. The pattern is mostly consistent but the price tools lack a domain prefix and vary in specificity, creating some inconsistency.
13 tools is a reasonable number for a server covering three domains. However, the redundant price tools could be consolidated, slightly reducing the count to improve focus.
The server is read-only: DragonSwap lacks swap execution, KiloLend lacks deposit/borrow/repay actions, and wallet info has no transaction capabilities. The price coverage is thorough but operational gaps are significant.