home / mcp / jupiter mcp server
An MCP server for executing token swaps on the Solana blockchain using Jupiter's new Ultra API.
Configuration
View docs{
"mcpServers": {
"kukapay-jupiter-mcp": {
"command": "node",
"args": [
"path/to/jupiter-mcp/server/index.js"
],
"env": {
"PRIVATE_KEY": "your private key",
"SOLANA_RPC_URL": "solana rpc url you can access"
}
}
}
}You deploy the Jupiter MCP Server to fetch swap orders and execute token swaps on Solana using Jupiter’s Ultra API. It combines price-efficient routing with RFQ and handles slippage and transaction landing to streamline automated swaps.
You use an MCP client to load and interact with the Jupiter MCP Server. Start by ensuring you have a compatible Node.js runtime, access to a Solana RPC endpoint, and a Solana private key for signing transactions. With the server configured, your client can fetch swap orders from Jupiter’s Ultra API and then execute those orders, leveraging slippage controls and priority fees to maximize success.
Prerequisites you must meet before installing the server.
Install and configure the MCP client to use the Jupiter MCP Server provided in this guide.
The client configuration to connect to the Jupiter MCP Server uses a local stdio setup. It runs a node-based server component and passes the required environment details so the MCP framework can initialize and communicate with Jupiter’s Ultra API.
Two primary tools are exposed for interaction with Jupiter’s Ultra API through the MCP server. Use them to fetch a swap order and then execute it.
Protect your Solana private key and ensure your SOLANA_RPC_URL points to a trusted RPC node. Do not expose private keys in client configurations or logs. Use environment-specific configurations for development, staging, and production.
Fetches a swap order from Jupiter's Ultra API, combining DEX routing and RFQ for optimal pricing and returning a base64-encoded transaction along with order details.
Submits the swap transaction to Jupiter via Ultra API, handling slippage, priority fees, and reporting the outcome including transactionId and swap events.