@recursa-ai/mcp

Model Context Protocol server exposing Recursa — the Solana yield aggregator — as MCP tools.

Drop-in for Claude Desktop, Cursor, Claude Code, or any MCP-compatible agent runtime. Once configured, the user can say "open a 2.5× JitoSOL loop with auto-rebalance" and the model has the data + math to answer authoritatively.

Install

npx @recursa-ai/mcp

That's it — no local install required. The first run downloads + caches.

Configure your client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "recursa": {
      "command": "npx",
      "args": ["@recursa-ai/mcp"]
    }
  }
}

Restart Claude Desktop. The new tools appear automatically.

Cursor

Edit .cursor/mcp.json in your project root with the same shape.

Claude Code

.claude/settings.json:

{
  "mcpServers": {
    "recursa": {
      "command": "npx",
      "args": ["@recursa-ai/mcp"]
    }
  }
}

Tools

Five tools are registered. Each wraps a single SDK call.

| Tool | What it does | |---|---| | list_strategies | List + filter the catalog (asset, risk, intent, protocol, search). Pre-sorted by net APY desc. | | preview_open_position | Quote net APY, health factor, liquidation price for a hypothetical position. Same math as the web /loop builder. | | get_rates | Raw rate snapshot, optionally filtered to one asset. | | find_emissions_arb | Surface "paid to borrow" opportunities (effectiveBorrowAPY < 0). | | explain_intent | Plain-English explanation of any of the 7 intent kinds. |

What you get out of the box

After install, you can ask Claude things like:

• "What's the best safe yield on USDC right now?"
• "Show me the top 5 SOL leveraged loops sorted by APY."
• "Preview a 2× SOL loop with 1 SOL of collateral."
• "Are there any emissions-arb opportunities right now?"
• "Explain CARRY strategies."

Claude calls the matching tool, gets real numbers, and answers truthfully. It will refuse to recommend leverage > 5× and will always surface liquidation price for leveraged previews — those are baked into the tool descriptions + the SKILL doc.

Transaction signing

The MCP server (and the underlying SDK) never sign. They build unsigned tx bytes for the caller to sign with whatever wallet they use. v0.1 of the SDK actually returns a stub error for tx building that directs to the web /loop?token=<asset>&leverage=<n> deep link; when the @recursa-ai/idl extraction lands, tx returns will be real base64 bytes the host can sign + submit.

License

MIT