jupiter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUPITER_API_KEY | No | Optional API key for higher rate limits; omit for keyless operation with 0.5 RPS |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jupiter_swap_quoteA | Get a swap quote via Jupiter's managed /order path. Returns the best price across all routers (Metis, RFQ, Dflow, OKX). |
| jupiter_swap_buildA | Get raw swap instructions for custom transaction construction. Use when composing Jupiter swaps with other instructions (flashloans, multi-step). Metis router only. |
| jupiter_token_searchA | Search for Solana tokens by name, symbol, or mint address. Returns metadata, verification status, organic scores, and trading metrics. |
| jupiter_token_infoA | Get detailed token metadata for a specific mint — verification status, organic score, daily volume, holder count. |
| jupiter_priceB | Get current USD prices for one or more Solana tokens. Pass mint addresses comma-separated. |
| jupiter_lend_depositA | Create a deposit transaction for Jupiter Lend Earn. Returns a base64-encoded unsigned transaction to sign and submit. |
| jupiter_lend_withdrawA | Create a withdraw transaction for Jupiter Lend Earn. Returns a base64-encoded unsigned transaction. |
| jupiter_limit_ordersA | Get all open limit orders for a wallet — pending trigger orders with price targets and amounts. |
| jupiter_limit_order_createA | Create a limit order. Returns a transaction to sign. Supports single, OCO (TP/SL), and OTOCO orders. |
| jupiter_limit_order_cancelB | Cancel one or more open limit orders. |
| jupiter_dca_ordersB | Get active DCA (Dollar Cost Average) orders for a wallet — recurring schedules and progress. |
| jupiter_dca_createA | Create a DCA order — recurring swap on a schedule. Returns transaction to sign. Example: buy $10 SOL every hour. |
| jupiter_prediction_eventsA | List Jupiter prediction events — binary markets on real-world events. Filter by category, sort by volume or date, include market data. |
| jupiter_perps_marketsA | List Jupiter perpetual futures markets — trading pairs, funding rates, open interest. |
| jupiter_perps_positionsA | Get open perpetual positions for a wallet — leverage, entry price, PnL, liquidation price. |
| jupiter_portfolioA | Get full portfolio for a wallet — all Jupiter positions across swaps, lending, DCA, limit orders, perps, and prediction markets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct Jupiter subdomain/action: swap quote vs build, token search vs info vs price, and read/transaction tools are clearly separated. The only close pair is token_search and token_info, but exact-mint detail vs search-by-query is explicit enough to avoid misselection.
All tools share the jupiter_<domain>_<action|resource> pattern with consistent snake_case and plural lists for collection queries. Small structural differences like token_info vs limit_order_create follow the resource shape rather than being arbitrary.
16 tools is at the upper edge but each is justified by the breadth of Jupiter's products: swap, tokens, lending, limit orders, DCA, prediction markets, perps, and portfolio. No redundant tools exist; each domain has a focused read/action pair.
The swap, token, lending, and limit-order surfaces are fairly complete, but DCA has no cancel/close tool and perps only exposes markets/positions with no order creation or closing. Prediction events are also list-only, leaving a few lifecycle dead ends for agents.