Trader MCP Server

Lavarage Trader MCP — hosted AI agent trading interface for Solana leveraged positions. That is what the trader mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Hosted MCP server for trading leveraged positions on Lavarage via AI agents (Claude, Cursor, GPT, custom agents).

The tools it exposes

The server publishes 9 tools. What each one is for:

• lavarage_login — Authenticate with Privy token
• lavarage_setup — Choose trading mode (unsigned or server-wallet)
• lavarage_list_tokens — List supported tokens with prices
• lavarage_get_rates — Lending rates and available liquidity
• lavarage_get_quote — Get a leverage trade quote
• lavarage_open_position — Open a leveraged position
• lavarage_close_position — Close a position
• lavarage_list_positions — List your positions
• lavarage_get_position — Get position details

What it needs from you

Configuration is passed through the environment: LAVARAGE_API_URL, LAVARAGE_API_KEY, PRIVY_APP_ID, PRIVY_APP_SECRET, PRIVY_SIGNING_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Trader's toolset — lavarage_login, lavarage_setup, lavarage_list_tokens and 6 more — is a fair guide to whether it matches your workflow. It is maintained by androit; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Trader's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Trader.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.