haiku-mcp-server

Haiku MCP Server is an MCP (Model Context Protocol) server that enables AI agents to execute blockchain transactions through the Haiku API. It is aimed at developers and AI agents who want to automate transactions and strategies in a multi-chain DeFi environment.

Main capabilities include:

• Token discovery: list tokens and DeFi assets supported by 21 blockchain networks, filterable by network or token category. Token categories cover native tokens, collateral tokens (such as Aave aTokens), variable debt tokens (such as Aave variable debt tokens), yield vaults (such as Yearn/Morpho), weighted liquidity (such as Balancer LP tokens), and concentrated liquidity (such as Uniswap V3 LP positions).
• Balance checking: retrieve token balances for a wallet address across all supported chains.
• Transaction quotes: obtain quotes for token swaps or portfolio rebalancing. Quotes are valid for 5 minutes, and it is recommended to execute as soon as possible to avoid transaction failure caused by price movements. Quotes require input positions, target weights, and optional slippage, and can specify a receiving wallet address.
• Transaction construction: convert quotes into unsigned EVM transactions.
• Wallet integration: extract EIP-712 payloads for signing by external wallets (such as Coinbase, AgentKit, Safe, etc.).
• Self-contained execution: optionally enable end-to-end execution by setting the WALLET_PRIVATE_KEY environment variable.
• Yield discovery: find the highest-yield DeFi opportunities across protocols and chains, filterable by APY, TVL, and category, with support for sorting and limiting the number of results.
• Portfolio analysis: analyze the assets held by a wallet and provide relevant yield opportunities based on actual holdings, including collateral health factors, etc.

Usage: The server can be run directly via npx, and can also be configured for clients such as Claude Desktop. Environment variables can be set, and the API also works without a key, but providing a key unlocks higher rate limits. Two transport modes are supported: Stdio (default, for Claude Desktop, Cursor, etc.) and Streamable HTTP (for remote hosting, Smithery, and web-based MCP clients), with HTTP endpoints including POST /mcp and GET /health.

There are two modes for transaction signing:

• Self-contained mode (set WALLET_PRIVATE_KEY): haiku_execute internally signs everything and broadcasts it, returning the transaction hash, with no external signing required.
• External wallet mode (no WALLET_PRIVATE_KEY): broadcast: false must be set; haiku cannot sign or broadcast. If haiku_execute is called with broadcast: true and no WALLET_PRIVATE_KEY, the server will return an error and instruct you to set broadcast: false, and to broadcast the returned transaction via the wallet MCP. If the quote contains approvals, each approval transaction must first be broadcast via the wallet MCP and confirmed. If Permit2 or bridge signing is required, you must first call haiku_prepare_signatures to obtain the standardized EIP-712 payload, sign it via the wallet MCP, and then pass the signature to haiku_execute.
• Cross-chain bridge signing: for cross-chain swaps, the quote may return isComplexBridge: true, indicating that a bridge intent signature is required. In self-contained mode, pass bridgeSigningPayload to haiku_execute; in external wallet mode, call haiku_prepare_signatures to obtain the normalized bridgeIntent payload, sign it, and pass it as userSignature.

Tokens are identified using the IID format: chainSlug:tokenAddress, for example arb:0x82aF... represents WETH on Arbitrum.

Use cases:

• AI agents executing multi-chain DeFi transactions, including swaps, providing liquidity, lending, bridging, and yield strategies.
• Discovering high-yield opportunities, querying the best lending yields or high APY vaults on a specific chain.
• Analyzing and optimizing wallet portfolios, combining yield discovery and transaction quote execution strategies.

Limitations:

• Quotes are valid for 5 minutes and must be executed as soon as possible.
• Without WALLET_PRIVATE_KEY, self-signing and broadcasting are not possible, and an external wallet MCP must be relied upon.
• In external wallet mode, if the quote contains approvals, the approval transactions must be broadcast first.
• Cross-chain swaps may require additional bridge signatures.
• The specific list of 22 supported chains is in the materialsand is not fully listed; only some examples such as Arbitrum and Base are mentioned.
• Other features, fees, prices, platforms, or effects not explicitly stated in the materials are not provided for now.