Server Details
Jupiter - 4 tools for swap quotes, liquidity pools, and trading data
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- junct-bot/jupiter-mcp
- GitHub Stars
- 0
See and control every tool call
Log every tool call with full inputs and outputs
Control which tools are enabled per connector
Manage credentials once, use from any MCP client
Monitor uptime and get alerted when servers go down
Available Tools
4 toolsprogram_id_to_label_getInspect
program-id-to-label — Returns a hash, which key is the program id and value is the label. This is used to help map error from transaction by identifying the fault program id. This can be used in conjunction with the excludeDexes or dexes parameter.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
quote_getInspect
quote — Request for a quote to be used in POST /swap Returns: { inputMint: string, inAmount: string, outputMint: string, ... }.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dexes | No | - Multiple DEXes can be pass in by comma separating them - For example: `dexes=Raydium,Orca+V2,Meteora+DLMM` - If a DEX is indicated, the route will **only use** that DEX - Full list of DEXes here: https://lite-api.jup.ag/swap/v1/program-id-to-label | |
| amount | Yes | - Raw amount to swap (before decimals) - Input Amount if `SwapMode=ExactIn` - Output Amount if `SwapMode=ExactOut` | |
| swapMode | No | - ExactOut is for supporting use cases where you need an exact output amount - In the case of `ExactIn`, the slippage is on the output token - In the case of `ExactOut`, the slippage is on the input token - Not all AMMs support `ExactOut`: Currently only Orca Whirlpool, Raydium CLMM, Raydium CPMM - We do not recommend using `ExactOut` for most use cases | |
| inputMint | Yes | query parameter: inputMint (string) | |
| outputMint | Yes | query parameter: outputMint (string) | |
| maxAccounts | No | - Rough estimate of the max accounts to be used for the quote - Useful if composing your own transaction or to be more precise in resource accounting for better routes | |
| slippageBps | No | - Default: 50 - This is threshold denoted in basis points. - If exact in and output amount exceeds the threshold, then the swap transaction will fail. | |
| excludeDexes | No | - Multiple DEXes can be pass in by comma separating them - For example: `excludeDexes=Raydium,Orca+V2,Meteora+DLMM` - If a DEX is indicated, the route will **not use** that DEX - Full list of DEXes here: https://lite-api.jup.ag/swap/v1/program-id-to-label | |
| platformFeeBps | No | - Take fees in basis points - If `platformFeeBps` is passed in, the `feeAccount` in `/swap` must be passed as well | |
| dynamicSlippage | No | - No longer applicable, only required to pass in via `/swap` endpoint | |
| onlyDirectRoutes | No | - Direct route limits Jupiter routing to single hop routes only - This may result in worse routes | |
| instructionVersion | No | - The version of instruction to use in the swap program | |
| asLegacyTransaction | No | - Instead of using versioned transaction, this will use the legacy transaction | |
| restrictIntermediateTokens | No | - Restrict intermediate tokens within a route to a set of more stable tokens - This will help to reduce exposure to potential high slippage routes |
swap_instructions_postInspect
swap-instructions — Request for swap instructions that you can use from the quote you get from /quote Returns: { otherInstructions: { programId: string, accounts: unknown[], data: string }[], computeBudgetInstructions: { programId: string, accounts: unknown[], data: string }[], setupInstructions: { programId: string, accounts: unknown[], data: string }[], ... }.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| payer | No | - Allow a custom payer to pay for the transaction fees and rent of token accounts - Note that users can close their ATAs elsewhere and have you reopen them again, your fees should account for this | |
| feeAccount | No | - An initialized token account that will be used to collect fees - The mint of the token account **can only be either the input or output mint of the swap** - Swap API no longer requires the use of the Referral Program - If `platformFeeBps` is passed in `/quote`, the `feeAccount` must be passed as well | |
| quoteResponse | Yes | quoteResponse ({ inputMint: string, inAmount: string, outputMint: string, outAmount: string, otherAmountThreshold: string, instructionVersion: "V1" | "V2", ... }) | |
| userPublicKey | Yes | userPublicKey (string) | |
| dynamicSlippage | No | - When enabled, it estimates slippage and apply it in the swap transaction directly, overwriting the `slippageBps` parameter in the quote response. - This is no longer maintained, we are focusing efforts on RTSE on Ultra Swap API | |
| trackingAccount | No | - Specify any public key that belongs to you to track the transactions - Useful for integrators to get all the swap transactions from this public key - Query the data using a block explorer like Solscan/SolanaFM or query like Dune/Flipside | |
| wrapAndUnwrapSol | No | - To automatically wrap/unwrap SOL in the transaction, as WSOL is an SPL token while native SOL is not - When true and input mint is SOL, it will wrap the SOL amount to WSOL and swap - When true and output mint is SOL, it will unwrap the WSOL back to SOL - When false and input mint is SOL, it will use existing WSOL amount to swap - When false and output mint is SOL, it will not unwrap the WSOL to SOL - To set this parameter to false, you need to have the WSOL token account initialized | |
| useSharedAccounts | No | - The default is determined dynamically by the routing engine, allowing us to optimize for compute units, etc - This enables the usage of shared program accounts, this is essential as complex routing will require multiple intermediate token accounts which the user might not have - If true, you do not need to handle the creation of intermediate token accounts for the user - Do note, shared accounts route will fail on some new AMMs (low liquidity token) | |
| asLegacyTransaction | No | - Builds a legacy transaction rather than the default versioned transaction - Used together with `asLegacyTransaction` in `/quote`, otherwise the transaction might be too large | |
| blockhashSlotsToExpiry | No | - Pass in the number of slots we want the transaction to be valid for - Example: If you pass in 10 slots, the transaction will be valid for ~400ms * 10 = approximately 4 seconds before it expires | |
| destinationTokenAccount | No | - Public key of a token account that will be used to receive the token out of the swap - If not provided, the signer's token account will be used - If provided, we assume that the token account is already initialized - `destinationTokenAccount` and `nativeDestinationAccount` are mutually exclusive | |
| dynamicComputeUnitLimit | No | - When enabled, it will do a swap simulation to get the compute unit used and set it in ComputeBudget's compute unit limit - This incurs one extra RPC call to simulate this - We recommend to enable this to estimate compute unit correctly and reduce priority fees needed or have higher chance to be included in a block | |
| nativeDestinationAccount | No | - Public key of an account that will be used to receive the native SOL token out of the swap - If not provided, the swap will default unwrap the WSOL and transfer the native SOL to the swap authority account - If provided, we will unwrap the WSOL and transfer the native SOL to the account - Only works if the output mint is SOL, is using the V2 instructions and the account passed in is not owned by token program - When sending native SOL to a new account, you must swap at least enough to cover the rent required to create it. - `destinationTokenAccount` and `nativeDestinationAccount` are mutually exclusive | |
| skipUserAccountsRpcCalls | No | - When enabled, it will not do any additional RPC calls to check on required accounts - The returned swap transaction will still attempt to create required accounts regardless if it exists or not | |
| prioritizationFeeLamports | No | - To specify a level or amount of additional fees to prioritize the transaction - It can be used for EITHER priority fee OR Jito tip (not both at the same time) - If you want to include both, you will need to use `/swap-instructions` to add both at the same time - Defaults to `auto`, but preferred to use `priorityLevelWithMaxLamports` as it may be more accurate when accounting local fee market - Fixed lamports can be passed in as an integer in the `prioritizationFeeLamports` parameter | |
| computeUnitPriceMicroLamports | No | - To use an exact compute unit price to calculate priority fee - `computeUnitLimit (1400000) * computeUnitPriceMicroLamports` - We recommend using `prioritizationFeeLamports` and `dynamicComputeUnitLimit` instead of passing in your own compute unit price |
swap_postInspect
swap — Request for a base64-encoded unsigned swap transaction based on the /quote response Returns: { swapTransaction: string, lastValidBlockHeight: number, prioritizationFeeLamports: number }.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| payer | No | - Allow a custom payer to pay for the transaction fees and rent of token accounts - Note that users can close their ATAs elsewhere and have you reopen them again, your fees should account for this | |
| feeAccount | No | - An initialized token account that will be used to collect fees - The mint of the token account **can only be either the input or output mint of the swap** - Swap API no longer requires the use of the Referral Program - If `platformFeeBps` is passed in `/quote`, the `feeAccount` must be passed as well | |
| quoteResponse | Yes | quoteResponse ({ inputMint: string, inAmount: string, outputMint: string, outAmount: string, otherAmountThreshold: string, instructionVersion: "V1" | "V2", ... }) | |
| userPublicKey | Yes | userPublicKey (string) | |
| dynamicSlippage | No | - When enabled, it estimates slippage and apply it in the swap transaction directly, overwriting the `slippageBps` parameter in the quote response. - This is no longer maintained, we are focusing efforts on RTSE on Ultra Swap API | |
| trackingAccount | No | - Specify any public key that belongs to you to track the transactions - Useful for integrators to get all the swap transactions from this public key - Query the data using a block explorer like Solscan/SolanaFM or query like Dune/Flipside | |
| wrapAndUnwrapSol | No | - To automatically wrap/unwrap SOL in the transaction, as WSOL is an SPL token while native SOL is not - When true and input mint is SOL, it will wrap the SOL amount to WSOL and swap - When true and output mint is SOL, it will unwrap the WSOL back to SOL - When false and input mint is SOL, it will use existing WSOL amount to swap - When false and output mint is SOL, it will not unwrap the WSOL to SOL - To set this parameter to false, you need to have the WSOL token account initialized | |
| useSharedAccounts | No | - The default is determined dynamically by the routing engine, allowing us to optimize for compute units, etc - This enables the usage of shared program accounts, this is essential as complex routing will require multiple intermediate token accounts which the user might not have - If true, you do not need to handle the creation of intermediate token accounts for the user - Do note, shared accounts route will fail on some new AMMs (low liquidity token) | |
| asLegacyTransaction | No | - Builds a legacy transaction rather than the default versioned transaction - Used together with `asLegacyTransaction` in `/quote`, otherwise the transaction might be too large | |
| blockhashSlotsToExpiry | No | - Pass in the number of slots we want the transaction to be valid for - Example: If you pass in 10 slots, the transaction will be valid for ~400ms * 10 = approximately 4 seconds before it expires | |
| destinationTokenAccount | No | - Public key of a token account that will be used to receive the token out of the swap - If not provided, the signer's token account will be used - If provided, we assume that the token account is already initialized - `destinationTokenAccount` and `nativeDestinationAccount` are mutually exclusive | |
| dynamicComputeUnitLimit | No | - When enabled, it will do a swap simulation to get the compute unit used and set it in ComputeBudget's compute unit limit - This incurs one extra RPC call to simulate this - We recommend to enable this to estimate compute unit correctly and reduce priority fees needed or have higher chance to be included in a block | |
| nativeDestinationAccount | No | - Public key of an account that will be used to receive the native SOL token out of the swap - If not provided, the swap will default unwrap the WSOL and transfer the native SOL to the swap authority account - If provided, we will unwrap the WSOL and transfer the native SOL to the account - Only works if the output mint is SOL, is using the V2 instructions and the account passed in is not owned by token program - When sending native SOL to a new account, you must swap at least enough to cover the rent required to create it. - `destinationTokenAccount` and `nativeDestinationAccount` are mutually exclusive | |
| skipUserAccountsRpcCalls | No | - When enabled, it will not do any additional RPC calls to check on required accounts - The returned swap transaction will still attempt to create required accounts regardless if it exists or not | |
| prioritizationFeeLamports | No | - To specify a level or amount of additional fees to prioritize the transaction - It can be used for EITHER priority fee OR Jito tip (not both at the same time) - If you want to include both, you will need to use `/swap-instructions` to add both at the same time - Defaults to `auto`, but preferred to use `priorityLevelWithMaxLamports` as it may be more accurate when accounting local fee market - Fixed lamports can be passed in as an integer in the `prioritizationFeeLamports` parameter | |
| computeUnitPriceMicroLamports | No | - To use an exact compute unit price to calculate priority fee - `computeUnitLimit (1400000) * computeUnitPriceMicroLamports` - We recommend using `prioritizationFeeLamports` and `dynamicComputeUnitLimit` instead of passing in your own compute unit price |
Verify Ownership
This connector has been claimed. The /.well-known/glama.json file has been verified and ownership is confirmed.
Glama periodically re-verifies ownership. If the file is removed, the claim will be revoked.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Try in Browser
Your Connectors
Sign in to create a connector for this server.