Trade Router MCP Server

Non-custodial Solana swap & limit order engine for AI agents — MCP server for TradeRouter.ai.

Remote serverstreamable-httpPython

What is the Trade Router MCP MCP server?

Non-custodial Solana swap & limit order engine for AI agents — MCP server for TradeRouter.ai. That is what the trade router mcp 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

  1. Agent calls build_swap → MCP sends wallet address (public key) to api.traderouter.ai 2. API returns an unsigned transaction 3. MCP signs the tx locally using TRADEROUTER_PRIVATE_KEY 4. The signed transaction is submitted to /protect (Jito MEV-protected bundle) 5. Server confirms and returns balance changes. The private key never crosses the network.

The tools it exposes

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

  • get_wallet_address — Get the configured wallet's public address
  • build_swap — Build an unsigned swap transaction
  • submit_signed_swap — Submit a manually signed transaction
  • auto_swap — Build + sign + submit in one call
  • get_holdings — Get token holdings for a wallet
  • get_mcap — Market cap and price for a token
  • get_flex_card — Trade card PNG URL for wallet + token
  • place_limit_order — Limit buy/sell by price or market cap
  • place_trailing_order — Trailing stop buy/sell
  • place_twap_order — TWAP (time-weighted) buy/sell
  • place_limit_twap_order — Limit trigger → TWAP execution
  • place_trailing_twap_order — Trailing trigger → TWAP execution

What it needs from you

Configuration is passed through the environment: TRADEROUTER_PRIVATE_KEY, SOLANA_RPC_URL. 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.

  • Node.js ≥ 18 - A Solana wallet private key in base58 format (use a dedicated trading wallet, not your main holdings)

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

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Trade Router MCP's toolset — get_wallet_address, build_swap, submit_signed_swap and 11 more — is a fair guide to whether it matches your workflow. It is maintained by traderouter; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

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 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Trade Router MCP.
  • 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.

Available tools

ToolWhat it does
get_wallet_addressGet the configured wallet's public address
build_swapBuild an unsigned swap transaction
submit_signed_swapSubmit a manually signed transaction
auto_swapBuild + sign + submit in one call
get_holdingsGet token holdings for a wallet
get_mcapMarket cap and price for a token
get_flex_cardTrade card PNG URL for wallet + token
place_limit_orderLimit buy/sell by price or market cap
place_trailing_orderTrailing stop buy/sell
place_twap_orderTWAP (time-weighted) buy/sell
place_limit_twap_orderLimit trigger → TWAP execution
place_trailing_twap_orderTrailing trigger → TWAP execution
place_limit_trailing_orderLimit trigger → trailing execution (single swap on trigger)
place_limit_trailing_twap_orderLimit trigger → trailing trigger → TWAP execution

How to install the Trade Router MCP MCP server

{
  "mcpServers": {
    "trade-router": {
      "command": "npx",
      "args": ["-y", "@traderouter/trade-router-mcp"],
      "env": {
        "TRADEROUTER_PRIVATE_KEY": "your-value",
        "SOLANA_RPC_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js ≥ 18 - A Solana wallet private key in base58 format (use a dedicated trading wallet, not your main holdings)
VariableDescriptionRequired
TRADEROUTER_PRIVATE_KEYCredential the server authenticates with.Yes
SOLANA_RPC_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Trade Router MCP to get wallet address.
  • Use Trade Router MCP to build swap.
  • Use Trade Router MCP to submit signed swap.

Frequently asked questions

It connects Trade Router MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_wallet_address, build_swap, submit_signed_swap, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Trade Router MCP directly.