Jupiter MCP

What araa47/jupiter-mcp MCP server does

The araa47/jupiter-mcp MCP server connects an MCP client to Jupiter’s Solana APIs. It covers two transaction workflows: immediate swaps through Jupiter Ultra API and limit orders through the Trigger API. It also exposes read-oriented operations for wallet balances, token discovery, token security information, and order history.

Immediate swaps return a quote and an unsigned transaction, then accept a signed transaction for execution. Limit-order tools create, execute, cancel, and query orders. This makes the server suitable for agents that need to inspect Solana assets, prepare trades, or manage orders from an MCP-compatible client.

How it works

The server runs locally through uvx, using the repository as its package source. MCP configuration supplies environment variables for the Solana RPC endpoint, network, timeout, and wallet private key. The default examples target Solana mainnet-beta.

The available tools are divided between Jupiter’s Ultra API and Trigger API. Quote, balance, token search, security, and order-management requests are listed as free by the project. Swap and limit-order execution are marked as paid API operations. Solana network fees and the financial consequences of real trades are separate considerations.

Setup and configuration

The documented quick-start command uses uvx with the GitHub repository and the jupiter-mcp executable:

{
  "command": "uvx",
  "args": [
    "--from",
    "git+https://github.com/araa47/jupiter-mcp",
    "jupiter-mcp"
  ]
}

Set PRIVATE_KEY to a base58-encoded Solana private key, such as one exported from Phantom. SOLANA_RPC_URL defaults to https://api.mainnet-beta.solana.com; SOLANA_NETWORK is shown as mainnet-beta; and REQUEST_TIMEOUT is shown as 30 seconds. The README also documents loading secrets from a .env file through envmcp.

Claude Desktop users can install the published jupiter-mcp-latest.dxt extension after installing Node.js, npx, uv, and uvx. Cursor users are given a dedicated installation link, but it requires replacing the example private-key value. Local development requires Python 3.12 or newer, uv, and direnv.

Tools and capabilities

The araa47/jupiter-mcp MCP server documents these tools:

• get_swap_quote: obtains a swap quote and unsigned transaction from input and output mint addresses plus an amount.
• execute_swap_transaction: submits a signed swap transaction using its transaction data and request ID.
• get_balances: retrieves token balances for a specified or configured wallet.
• get_shield: returns token security information for supplied mint addresses.
• search_token: searches for tokens by query.
• create_limit_order: creates a limit-order transaction with amounts and optional slippage or expiration settings.
• execute_limit_order: submits a signed limit-order transaction.
• cancel_limit_order and cancel_limit_orders: cancel one or multiple orders.
• get_limit_orders: filters active or historical orders by status and optional wallet, mint, or page parameters.

The repository includes free tests for quotes, balances, searches, security checks, and mocked execution. Tests that broadcast real trades require an explicit paid-test flag and use small or deliberately non-executable order values according to the README.

Limitations and notes

A private key is required for the documented configuration, so it should be kept outside shared MCP configuration where possible. The default setup points at mainnet-beta, and the project includes tests that can spend SOL when real execution is enabled. Confirm wallet, mint, amount, network, and order parameters before allowing an agent to execute transactions.

The README identifies some Jupiter execution operations as paid, but it does not specify pricing details. It also does not state a software license in the provided material.