Jupiter MCP Server

Jupiter MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. An MCP server for executing token swaps on the Solana blockchain using Jupiter's new Ultra API.

What you get

• Fetch swap orders from Jupiter's Ultra API, combining DEX routing and RFQ (Request for Quote) for optimal pricing
• Execute swaps via Jupiter's Ultra API, handling slippage, priority fees, and transaction landing

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Jupiter is connected, these are the calls the assistant has available:

• Description — Fetches a swap order from Jupiter's Ultra API, leveraging both DEX routing and RFQ for optimal pricing
• Inputs — - inputMint: Input token mint address (e.g., SOL or token pubkey)
• outputMint — Output token mint address (e.g., USDC or token pubkey)
• amount — Input amount as a string (e.g., "1.23")
• slippageBps — Slippage tolerance in basis points (e.g., 50 for 0.5%)
• Output — JSON with requestId, transaction (base64-encoded), inputMint, outputMint, inAmount, outAmount, price
• transaction — Base64-encoded transaction from get-ultra-order

Configuration and credentials

You will need 2 environment variables: SOLANA_RPC_URL, PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js: Version 18 or higher (for native fetch support). - Solana Wallet: A private key (base58-encoded) for signing transactions. - RPC Endpoint: Access to a Solana RPC node (e.g., https://api.mainnet-beta.solana.com).

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the jupiter mcp server does with a few real requests.

Choosing this one

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. Jupiter's toolset — Description, Inputs, outputMint and 4 more — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.