概要
What is Jupiter Solana Mcp Server?
The Jupiter Solana Mcp Server is an MCP (Model Context Protocol) server that integrates with Jupiter Protocol on Solana, enabling token swaps, token search, portfolio management, and intelligent error diagnostics. It is designed for developers building on Solana who need a programmatic interface to Jupiter’s Ultra API.
How to use Jupiter Solana Mcp Server?
Install Node.js 18+, clone the repository, run npm install, configure a .env file with SOLANA_RPC_URL, PRIVATE_KEY, and JUPITER_API_KEY, then add the server to your MCP client configuration using "command": "node", "args": ["path/to/jupiter-mcp/index.js"]. Use the provided tools (search-token, get-balances, get-ultra-order, execute-ultra-order) to interact with Solana tokens.
Key features of Jupiter Solana Mcp Server
- Token swaps via Jupiter’s Ultra API with intelligent slippage and fee handling
- Token search by symbol, name, or mint address with detailed market data
- Portfolio management with token balances and holdings
- Intelligent error detection and helpful user guidance
- Automatic SOL fee validation before transaction execution
- Multi‑language support (English)
Use cases of Jupiter Solana Mcp Server
- Searching for token information, price, volume, and security audit data
- Checking wallet balances of SOL and all SPL tokens
- Obtaining optimized swap quotes for token trading
- Executing swap transactions with status monitoring and error handling
- Building automated trading or portfolio monitoring tools
FAQ from Jupiter Solana Mcp Server
What dependencies are required?
Node.js 18 or higher, a free Jupiter API key (from portal.jup.ag), a base58-encoded Solana private key, and a Solana RPC endpoint (e.g., https://api.mainnet-beta.solana.com).
How does the server handle transaction errors?
It provides intelligent error messages for insufficient SOL, slippage issues, and network problems, with suggestions such as adding 0.01 SOL or increasing slippage tolerance.
Can I check balances of any wallet?
Yes, the get-balances tool accepts an optional walletAddress parameter; if omitted it defaults to the configured wallet.
Where does my private key live?
The private key is stored locally in the .env file and is only used for signing transactions within the server; it is never sent externally.
What transports and authentication are used?
The server uses standard MCP transport (stdio via command/args) and authenticates to the Jupiter API using the JUPITER_API_KEY environment variable.
