jupiter

The Jupiter MCP server exposes a set of tools that allow Claude to interact with Jupiter's Portfolio and Price APIs. It includes portfolio tools for viewing wallet positions, staked JUP tokens, and platform coverage, as well as price tools that fetch real-time token prices on the Solana blockchain. The available tools are: jupiter_get_positions to retrieve portfolio positions across wallets and activity (balances, staked positions, liquidity pools, farming, vaults, lending, etc.); jupiter_get_staked_jup to fetch information about staked JUP and unstaking positions; jupiter_get_platforms to list all DeFi platforms integrated with Jupiter's portfolio tracking; and jupiter_get_price to obtain current prices for one or more tokens, including USD price, 24h changes, and token decimals. To use these tools with Claude, configure the MCP server in Claude Desktop to point to the Jupiter MCP server and provide your Jupiter API key. Claude will then expose prompts that invoke these tools to fetch data and present it in natural language summaries.

Prerequisites: Node.js v16 or higher, npm, and a Jupiter API key. You will typically install and run the MCP server via npm or npx, optionally building from source if you prefer to run locally from a repository.

From npm (recommended):

1. Install globally and run:

# Install globally
npm install -g jupiter-mcp-server

# Run with npx (or simply
npx jupiter-mcp-server

From source:

1. Clone the repository:

git clone https://github.com/quanghuynguyen1902/jupiter-mcp-server.git
cd jupiter-mcp-server

2. Install dependencies:

npm ci

3. Build the project (if applicable):

npm run build

4. Run locally (example):

node build/index.js

Configuration (environment): ensure JUPITER_API_KEY is set either via environment or a .env file:

export JUPITER_API_KEY=your_jupiter_api_key_from_portal

Environment variables: JUPITER_API_KEY is required for authenticating with Jupiter APIs. If you encounter 401 errors, double-check the API key and that there are no extra spaces or quotes. When running via Claude Desktop, you can supply the key in the mcpServers configuration under env. If running locally, you can use a .env file placed in the server root. Logs can help diagnose API rate limits or network issues; monitor for 429 or 503 responses from Jupiter APIs. If you update the server code, rebuild before restarting Claude Desktop or reloading the MCP server. The server currently relies on the Jupiter Portfolio v1 and Price v3 endpoints accessible at https://api.jup.ag/portfolio/v1 and https://api.jup.ag/price/v3 respectively.