MCP Integration
Kairu exposes its full intelligence layer via the Model Context Protocol. This is the real synergy in Kairu: your position data, market data, and signal state aren't locked inside Kairu's own chat — they're exposed as composable tools that any MCP-compatible AI can call alongside its own reasoning and its own other tools. Connect once, and Claude (or your own agent) can check your signals, pull your position, and run a simulation in a single turn, without Kairu's chat being involved at all.
The endpoint
GET https://app.kairu.finance/api/mcp
This endpoint exposes all 13 Kairu tools plus conversation management, following the MCP specification.
What needs authentication
Not every tool needs your Bearer token. Kairu's tools split into two tiers:
11 tools — no auth required
get_position, get_liquidation_info, get_market_data, get_reserve_details, get_apy_history, simulate, analyze_e_mode, get_rewards, get_gho_position, get_transaction_history, get_signals all take a wallet address directly as an argument. Any MCP client can call them — authenticated or not — simply by telling the AI which wallet address to check.
2 tools — Bearer token required
get_portfolio and simulate_portfolio resolve your saved wallet groups by account, so they only work with a valid Bearer token attached — there's no wallet address that substitutes for your logged-in session here.
This is why ChatGPT — which can't attach your static Bearer token — still works for most of Kairu's tools, and only the two portfolio-aggregation tools are unavailable there (see below).
Authentication (for the 2 tools that need it)
The MCP endpoint uses Bearer token authentication. Your token is the same session token issued when you sign in with SIWE on the web app.
To retrieve your token:
- Sign in at app.kairu.finance
- Go to Settings → MCP
- Copy your Bearer token
The token expires after 30 days (same as the web session).
Connecting your AI client
Claude Desktop and Claude.ai (web) both connect the same way — a remote MCP server is added once as a custom connector and reached from Anthropic's cloud, regardless of which Claude client you're using.
Open Connectors settings
Go to Settings → Connectors and click the + button next to Connectors. This screen is identical in Claude Desktop and on claude.ai.
Add the server URL
Paste https://app.kairu.finance/api/mcp as the connector's remote MCP URL.
Add your Bearer token (optional, for portfolio tools)
Open Advanced settings and add a request header if you want get_portfolio / simulate_portfolio available:
Authorization: Bearer YOUR_TOKEN_HERE
Claude stores the header value securely and never displays it again after saving. Skip this step entirely if you only need the 11 no-auth tools.
Save, then enable per conversation
Click Add. In any chat, use the + button → Connectors to toggle Kairu on for that conversation.
ChatGPT's Developer Mode custom connectors only authenticate via OAuth or no-auth — there's no field to attach a static Bearer token like Kairu's. That means the 2 Bearer-only tools (get_portfolio, simulate_portfolio) aren't reachable, but the other 11 tools work with no authentication at all.
Enable Developer Mode
Go to Settings → Connectors → Advanced → Developer Mode. Team/Enterprise workspaces need an admin to enable this first.
Add the custom connector
Click Add custom connector and paste https://app.kairu.finance/api/mcp as the server URL. Leave authentication unset — Kairu's server doesn't require it for these tools.
Ask with a wallet address
Since there's no session to identify you, tell ChatGPT which wallet to check, e.g. "Using Kairu, check the health factor for wallet 0xABC...123."
Le Chat's custom connectors support Bearer token headers directly, so all 13 tools are reachable, same as Claude.
Open the Connectors page
Go to Connectors → + Add Connector and switch to the Custom MCP Connector tab.
Fill in the connector details
- Connector name:
Kairu - Server URL:
https://app.kairu.finance/api/mcp
Authenticate
Le Chat detects the server's authentication method automatically. When prompted for credentials, provide your Bearer token from Settings → MCP in the Authorization header.
Connect
Click Connect. Kairu's tools are then available to attach in any Le Chat conversation.
Any client that accepts a remote MCP server URL with custom headers (Cursor, Windsurf, a custom agent script, an MCP client library) can connect the same way.
{
"mcpServers": {
"kairu": {
"url": "https://app.kairu.finance/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE"
}
}
}
}
Omit the headers block entirely if you only need the 11 no-auth tools. Consult your client's documentation for where this configuration lives.
Available tools via MCP
All 13 Kairu tools are available via MCP, grouped the same way as in AI Chat. Each card notes whether it needs your Bearer token.
Position & risk
get_position · get_liquidation_info · analyze_e_mode
Market data
get_market_data · get_reserve_details · get_apy_history
Simulation
simulate — six what-if action types, including a live CowSwap quote for swap-repay
Portfolio
get_portfolio · simulate_portfolio — resolve wallet groups by account, require a configured wallet group
Rewards & GHO
get_rewards · get_gho_position
Activity & signals
get_transaction_history · get_signals
Professional use cases
Fund manager risk dashboard. Connect Kairu to a Claude instance with access to your wallet group (Bearer token attached). Ask: "Give me a risk summary across all portfolio positions, flag any health factors below 1.5, and list the five largest single-asset liquidation exposures."
Automated position reporting. Use the MCP endpoint in a scheduled script with an MCP client library to generate daily position snapshots and send summaries to a Slack or Notion workspace.
Custom alert agents. Build a custom agent that polls get_signals every hour and triggers a workflow when specific signal combinations are active — no auth required.
Chained reasoning in one turn. Because signals, position data, and simulation are all separate tools on the same server, an external AI can chain them without any Kairu-specific glue code: "Check my active signals, then simulate what a 20% ETH drop does to my position, and tell me if I should worry." One prompt, three tool calls, zero context-switching.
Multi-protocol analysis. As Kairu adds support for Compound, Morpho, and Spark, the same MCP tools will return cross-protocol position data — letting you query your entire DeFi exposure in a single AI conversation, with no change to how your client is configured.