kaia

KAIA-MCP serves as an MCP-based bridge that lets AI agents interact with the KAIA blockchain and DeFi protocols. It exposes tooling to read blockchain data, query price information, and execute on-chain actions through a unified set of APIs and tools. With this server, you can use AI clients like Claude Desktop or Cursor.ai to request market data, fetch live prices, query wallet balances, simulate or perform transactions, and execute lending, borrowing, and DEX operations via the underlying KiloLend, DragonSwap, and price API integrations. The configuration shown enables your AI agent to connect using an MCP client, specify operation mode, and securely supply a wallet key for transaction-enabled workflows. You can switch between read-only (readonly) mode for analysis and transaction mode for actual on-chain activity by adjusting KAIA_AGENT_MODE and KAIA_PRIVATE_KEY.

Once running, you can leverage the available tools across modules: wallet tools for balance and transfers, KiloLend tools for lending operations, DragonSwap tools for quotes and swaps, and price API tools for real-time token pricing. This enables end-to-end interactions from data queries to executing trades or managing loans via an AI-assisted workflow.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Git (optional, for cloning the repository)
• Access to the KAIA RPC endpoint and a KAIA private key if you plan to operate in transaction mode

Installation steps:

1. Install dependencies

   • Run: npm install

2. Build the project (if required by the repository)

   • Run: npm run build

3. Run the MCP server configuration example (as shown below) or integrate into your deployment workflow

   • Ensure you have a .env file or environment variables set as described in the config snippet

4. Start the server (if needed locally)

   • Run: npm start

5. Verify the server is listening and reachable by your MCP client and AI tools

Notes:

• If you use transaction mode, ensure KAIA_PRIVATE_KEY is secured and never committed.
• In read-only mode, KAIA_PRIVATE_KEY can be omitted.

Tips and considerations:

• The KAIA_RPC_URL should point to a KAIA public or private node with proper permissions for the actions you intend to perform.
• KAIA_AGENT_MODE can be 'readonly' or 'transaction'. The latter enables on-chain operations but requires a valid private key.
• For production, rotate keys regularly and consider using a secure vault or secret manager to inject KAIA_PRIVATE_KEY.
• The tools exposed by this MCP server cover wallet operations, lending, and DragonSwap interactions. Use read-only mode for development or analytics and test transactions in a safe environment.
• If you encounter rate limits from price APIs or RPC endpoints, consider caching strategies or multiple API keys where supported.