search-tokenLABSCO SUMMARY
Swaps executed from the conversation, signed by a key you supply.
The pre-flight work is the thoughtful part — it checks the wallet holds enough SOL for fees and explains a failure rather than returning a raw RPC error — and the swap goes out under a private key you set in the environment.
What it is
A Node MCP server for Jupiter Protocol on Solana. It executes swaps via Jupiter's Ultra API with slippage and fee handling, searches tokens with market data attached, reads wallet balances, and validates that you hold enough SOL to cover transaction fees before submitting.
What you get
- A swap executed through Jupiter's Ultra API, with slippage and fee handling
- Tokens found by symbol, name or mint address, with market data
- Token balances and holdings across the wallet
- An automatic check that the wallet holds enough SOL for transaction fees
- Failures diagnosed with guidance instead of a raw RPC error
Requirements
Node.js 18 or higher, a Jupiter API key from the Jupiter portal, a Solana RPC endpoint, and a base58-encoded private key in PRIVATE_KEY. That key signs transactions, so the server can move funds out of that wallet.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Finding the right mint before you trade
Search by symbol, name or mint address and confirm which token you actually mean.
02
Checking what a token is worth right now
The search result carries market data, so pricing does not need a second source.
03
Executing a swap without opening a wallet UI
Route it through Jupiter's Ultra API with slippage handled, from the conversation.
04
Seeing what is actually in the wallet
Read the token balances and holdings before deciding what to move.
05
Working out why a transaction failed
The diagnostics name the cause — insufficient SOL for fees being the common one — instead of surfacing the RPC error.
4 tools
Listed in project docs. Your client may show a different list.
get-balancesget-ultra-orderexecute-ultra-orderBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- node on PATH
- Node.js 18 or later
- PRIVATE_KEY in your environment
- JUPITER_API_KEY in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
Configuration file
JSON
{
"mcpServers": {
"Jupiter-MCP": {
"command": "node",
"args": [
"<YOUR_PATH_TO_JUPITER_MCP>/index.js"
],
"env": {
"SOLANA_RPC_URL": "https://api.mainnet-beta.solana.com",
"PRIVATE_KEY": "<YOUR_PRIVATE_KEY>",
"JUPITER_API_KEY": "<YOUR_JUPITER_API_KEY>"
}
}
}
}node
TERMINAL
node <YOUR_PATH_TO_JUPITER_MCP>/index.js
