Jupiter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUPITER_API_KEY | Yes | Your Jupiter API key from https://portal.jup.ag/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jupiter_get_positionsA | Get portfolio positions for a Solana wallet address including wallet balances, staked positions, liquidity pools, farming, vaults, lending, and more |
| jupiter_get_staked_jupA | Get staked JUP tokens information for a Solana wallet address, including amount staked and unstaking positions |
| jupiter_get_platformsA | Get a list of all DeFi platforms integrated with Jupiter's portfolio tracking system |
| jupiter_get_priceA | Get current prices for one or more tokens on Jupiter, including USD price, 24h price change, and token decimals |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Tools are mostly distinct, but jupiter_get_positions includes staked positions while jupiter_get_staked_jup specifically covers staking, creating potential overlap. Descriptions help clarify the difference.
All tools follow the identical jupiter_get_ prefix with a clear noun suffix (positions, staked_jup, platforms, price). This is a perfectly consistent verb_noun pattern.
Four tools is well within the ideal range for a focused portfolio and price server. Each tool covers a distinct area, and the count feels neither sparse nor bloated.
The set covers core portfolio positions, staking details, platform listings, and prices. It lacks features like transaction history or swap execution, but that may not be the server's intended scope.