MCP Paradex Server
The MCP Paradex Server acts as a bridge between AI assistants (like Claude) and the Paradex perpetual futures trading platform, enabling AI-driven trading and analysis. With this server, you can:
Retrieve Market Data: Access price, volume, 24h change, funding rates, BBO, orderbooks, candlestick data (klines), and recent trades
Manage Trading Accounts: Track and manage accounts, vaults, balances, positions, trade fills, and funding payments
Place and Manage Orders: Create, cancel, and monitor trading orders with various order types
Monitor System State: Check system health, operational status, and maintenance schedules
Perform Advanced Analysis: Access historical data and conduct trading/risk analysis
Integration with AI Assistants: Seamlessly integrate with AI platforms like Claude via Smithery.ai
Access Documentation: Retrieve Paradex documentation as needed
Integrates with the Ethereum blockchain through the Paradex perpetual futures trading platform, requiring Ethereum private keys for authentication and trading functionality
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Paradex Server show me the current orderbook for ETH-PERP"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Paradex Server
Up to date supported version can be found here https://github.com/tradeparadex/mcp-paradex-py
Model Context Protocol (MCP) server implementation for the Paradex trading platform.
Overview
This project provides a bridge between AI assistants (like Claude) and the Paradex perpetual futures trading platform. Using the MCP standard, AI assistants can:
Retrieve market data from Paradex
Manage trading accounts and vaults
Place and manage orders
Monitor positions and balance
Related MCP server: MCP Paradex Server
Prerequisites
Python 3.10+
Installation
Quick Start
Cursor IDE
Click to automatically configure this MCP server in Cursor:
Claude Code CLI
claude mcp add paradex uvx mcp-paradexSmithery (Claude Desktop)
npx -y @smithery/cli install @sv/mcp-paradex-py --client claudeStandard Installation
PyPI
pip install mcp-paradexuvx (Recommended)
uvx mcp-paradexDevelopment Setup
Clone the repository:
git clone https://github.com/sv/mcp-paradex-py.git cd mcp-paradex-pyInstall development dependencies:
uv sync --dev --all-extrasRun locally:
uv run mcp-paradex
Configuration
Environment Variables
Set these environment variables for authentication:
PARADEX_ENVIRONMENT: Set toprod,testnet, ornightly(default:prod)PARADEX_ACCOUNT_PRIVATE_KEY: Your Paradex account private key
Using .env File
cp .env.template .env
# Edit .env with your credentialsClient Configuration
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"paradex": {
"command": "uvx",
"args": ["mcp-paradex"],
"env": {
"PARADEX_ENVIRONMENT": "testnet",
"PARADEX_ACCOUNT_PRIVATE_KEY": "your_private_key"
}
}
}
}Docker (local / stdio)
# Build image
docker build . -t sv/mcp-paradex-py
# Run (public only)
docker run --rm -i sv/mcp-paradex-py
# Run with trading capabilities
docker run --rm -e PARADEX_ACCOUNT_PRIVATE_KEY=your_key -i sv/mcp-paradex-pyDocker (AWS Lambda / HTTP)
Use Dockerfile.aws for remote deployments via AWS Lambda with the
Lambda Web Adapter.
The adapter bridges Lambda invocations to the server's HTTP endpoint,
so no Lambda-specific code is needed.
# Build
docker build -f Dockerfile.aws -t sv/mcp-paradex-py-aws .
# Test locally (mirrors Lambda config)
docker run --rm -p 8080:8080 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_STATELESS=true \
-e MCP_PORT=8080 \
-e PARADEX_ENVIRONMENT=prod \
sv/mcp-paradex-py-awsThe server will be available at http://localhost:8080/mcp.
Deploying to Lambda:
Push the image to ECR
Create a Lambda function from the container image
Set the Lambda Function URL invoke mode to
RESPONSE_STREAMSet environment variables on the Lambda function:
MCP_TRANSPORT=streamable-httpMCP_STATELESS=truePARADEX_ENVIRONMENT=prod(ortestnet)PARADEX_ACCOUNT_PRIVATE_KEY=your_key(optional, for trading)
Available Resources and Tools
Resources
System Resources
paradex://system/config- Get Paradex system configurationparadex://system/time- Get current system timeparadex://system/state- Get system operational state
Market Resources
paradex://markets- List of available marketsparadex://market/summary/{market_id}- Detailed market information
Vault Resources
paradex://vaults- List all vaultsparadex://vaults/config- Global vault configurationparadex://vaults/balance/{vault_id}- Vault balanceparadex://vaults/summary/{vault_id}- Comprehensive vault summaryparadex://vaults/transfers/{vault_id}- Deposit/withdrawal historyparadex://vaults/positions/{vault_id}- Current trading positionsparadex://vaults/account-summary/{vault_id}- Trading account information
Tools
System Tools
paradex_system_config- Get global system configurationparadex_system_state- Get current system state
Market Tools
paradex_markets- Get detailed market informationparadex_market_summaries- Get market summaries with metricsparadex_funding_data- Get historical funding rate dataparadex_orderbook- Get current orderbook with customizable depthparadex_klines- Get historical candlestick dataparadex_trades- Get recent tradesparadex_bbo- Get best bid and offer
Account Tools
paradex_account_summary- Get account summaryparadex_account_positions- Get current positionsparadex_account_fills- Get trade fillsparadex_account_funding_payments- Get funding paymentsparadex_account_transactions- Get transaction history
Order Tools
paradex_open_orders- Get all open ordersparadex_create_order- Create new orderparadex_cancel_orders- Cancel existing ordersparadex_order_status- Get order statusparadex_orders_history- Get historical orders
Vault Tools
paradex_vaults- Get detailed vault informationparadex_vaults_config- Get global vault configurationparadex_vault_balance- Get vault balanceparadex_vault_summary- Get comprehensive vault summaryparadex_vault_transfers- Get deposit/withdrawal historyparadex_vault_positions- Get current vault positionsparadex_vault_account_summary- Get vault trading account info
Trading Analysis Prompts
Market Analysis
market_overview- Comprehensive crypto market overviewmarket_analysis- Detailed technical and microstructure analysis
Position and Portfolio Management
position_management- Comprehensive position analysiscreate_optimal_order- Design optimal order parametershedging_strategy- Develop effective hedging strategiesportfolio_risk_assessment- Thorough portfolio risk analysisliquidation_protection- Identify and mitigate liquidation risks
Investment Strategies
vault_analysis- Comprehensive vault analysis for investment decisionsfunding_rate_opportunity- Identify funding rate arbitrage opportunitiestrading_consultation- Interactive trading advice and consultation
Documentation MCP
Enhanced results with Paradex documentation access:
"paradex-docs-mcp": {
"command": "uvx",
"args": [
"--from",
"mcpdoc",
"mcpdoc",
"--urls",
"Paradex:https://docs.paradex.trade/llms.txt",
"--transport",
"stdio"
]
}Contributing
Please see CONTRIBUTING.md for information on how to contribute to this project, development setup, and our coding standards.
License
Available Tools
16 toolsparadex_bboARead-only
Get the current best available prices for immediate execution decisions.
Use this tool when you need to:
- Make quick trading decisions without full orderbook depth
- Calculate current spread costs before placing orders
- Monitor real-time price changes efficiently
- Get a snapshot of current market conditions
- Determine fair mid-price for calculations
The BBO provides the most essential price information with minimal data,
perfect for quick decisions or when full orderbook depth isn't needed.
Example use cases:
- Calculating current trading spreads before placing orders
- Monitoring real-time price movements efficiently
- Determining execution prices for immediate market orders
- Calculating mid-price for order placement strategies
- Setting appropriate limit order prices to improve fill chances
Inputs: market_id (required).
paradex_filters_modelARead-only
Get detailed schema information to build precise data filters.
Use this tool when you need to:
- Understand exactly what fields are available for filtering
- Learn the data types and formats for specific fields
- Build complex JMESPath queries with correct syntax
- Create sophisticated filtering and sorting expressions
Knowing the exact schema helps you construct precise filters that
return exactly the data you need, avoiding trial and error.
Example use cases:
- Learning what fields exist in market data responses
- Finding the correct property names for filtering
- Understanding data types for numerical comparisons
- Building complex multi-criteria filters for large datasets
Inputs: tool_name (required).
paradex_funding_dataARead-only
Analyze funding rates for potential funding arbitrage or to understand holding costs.
Use this tool when you need to:
- Calculate expected funding payments for a position
- Find markets with extreme funding rates for potential arbitrage
- Understand historical funding patterns for a market
- Evaluate the cost of holding a position over time
This data is critical for perpetual futures traders to assess the carrying cost
of positions and identify potential funding arbitrage opportunities.
Example use cases:
- Finding markets with negative funding for "paid to hold" opportunities
- Calculating the funding component of a trade's P&L
- Comparing funding rates across different assets for relative value trades
- Analyzing funding rate volatility to predict potential rate changes
Inputs: market_id (required), start_unix_ms (required), end_unix_ms (required). Returns: object
paradex_klinesARead-only
Analyze historical price patterns for technical analysis and trading decisions.
Use this tool when you need to:
- Perform technical analysis on historical price data
- Identify support and resistance levels from price history
- Calculate indicators like moving averages, RSI, or MACD
- Backtest trading strategies on historical data
- Visualize price action over specific timeframes
Candlestick data is fundamental for most technical analysis and trading decisions,
providing structured price and volume information over time.
Example use cases:
- Identifying chart patterns for potential entries or exits
- Calculating technical indicators for trading signals
- Determining volatility by analyzing price ranges
- Finding significant price levels from historical support/resistance
- Measuring volume patterns to confirm price movements
Inputs: market_id (required), start_unix_ms (required), end_unix_ms (required), resolution. Returns: result
paradex_marketsARead-only
Find markets that match your trading criteria or get detailed market specifications.
Use this tool when you need to:
- Understand exact tick sizes and minimum order sizes before placing trades
- Find all markets for a specific asset (e.g., all BTC-based markets)
- Compare contract specifications across different markets
- Identify markets with specific characteristics for your trading strategy
Retrieves comprehensive details about specified markets, including
base and quote assets, tick size, minimum order size, and other
trading parameters. If "ALL" is specified or no market IDs are provided,
returns details for all available markets.
Example use cases:
- Finding the minimum order size for a new trade
- Identifying markets with the smallest tick size for precise entries
- Checking which assets are available for trading
`asset_kind` is the type of asset in the market. It can be `PERP` or `PERP_OPTION`.
You can use JMESPath expressions (https://jmespath.org/specification.html) to filter, sort, or limit the results.
Use the `paradex_filters_model` tool to get the filters for a tool.
Examples:
- Filter by base asset: "[?base_asset=='BTC']"
- Sort by 24h volume: "sort_by([*], &volume_24h)"
- Limit to top 5 by volume: "[sort_by([*], &to_number(volume_24h))[-5:]]"
Inputs: market_ids, jmespath_filter, limit, offset.
paradex_market_summariesARead-only
Identify the most active or volatile markets and get current market conditions.
Use this tool when you need to:
- Find the most active markets by volume for liquidity analysis
- Discover markets with significant price movements for momentum strategies
- Compare current prices across multiple assets
- Identify markets with unusual behavior for potential opportunities
Retrieves current market summary information including price, volume,
24h change, and other key market metrics. If "ALL" is specified or no market IDs
are provided, returns summaries for all available markets.
Example use cases:
- Finding high-volatility markets for short-term trading
- Identifying top gainers and losers for the day
- Comparing volume across different markets to find liquidity
- Getting the current price and 24-hour range for price analysis
You can use JMESPath expressions (https://jmespath.org/specification.html) to filter, sort, or limit the results.
Use the `paradex_filters_model` tool to get the filters for a tool.
Examples:
- Filter by high price: "[?high_price > `10000`]"
- Sort by volume: "sort_by([*], &volume)"
- Get top 3 by price change: "[sort_by([*], &to_number(price_change_percent))[-3:]]"
Inputs: market_ids, jmespath_filter, limit, offset.
paradex_orderbookARead-only
Analyze market depth and liquidity to optimize order entry and execution.
Use this tool when you need to:
- Assess true liquidity before placing large orders
- Identify potential support/resistance levels from order clusters
- Determine optimal limit order prices for higher fill probability
- Detect order imbalances that might signal price direction
Understanding the orderbook is essential for effective trade execution,
especially for larger orders or in less liquid markets.
Example use cases:
- Finding the optimal limit price to ensure your order gets filled
- Estimating potential slippage for market orders of different sizes
- Identifying large resting orders that might act as support/resistance
- Detecting order book imbalances that could predict short-term price moves
Inputs: market_id (required), depth. Returns: object
paradex_system_configARead-only
Understand the exchange's global parameters that affect all trading activity.
Use this tool when you need to:
- Check fee schedules before placing trades
- Verify trading limits and restrictions
- Understand exchange-wide parameters that affect your trading
- Keep up with changes to the exchange's configuration
This information provides important context for making trading decisions and
understanding how the exchange operates.
Example use cases:
- Checking current fee tiers for different markets
- Verifying maximum leverage available for specific markets
- Understanding global trading limits or restrictions
- Checking if any exchange-wide changes might affect your trading strategy
Inputs: no named parameters. Returns: starknet_gateway_url, starknet_fullnode_rpc_url, starknet_fullnode_rpc_base_url…
paradex_system_stateARead-only
Verify the exchange is fully operational before executing trades.
Use this tool when you need to:
- Check if Paradex is functioning normally before placing important orders
- Verify system status if you encounter unexpected behavior
- Confirm that maintenance periods are not in effect
- Check exchange clock synchronization with your own systems
This is especially important before executing critical trades or when
experiencing unexpected behavior from other API calls.
Example use cases:
- Verifying the exchange is operational before executing a trading strategy
- Checking if maintenance mode is active when experiencing delays
- Confirming exchange status during periods of market volatility
- Diagnosing API issues by checking system health
Inputs: no named parameters. Returns: Model representing the current state of the Paradex system.
paradex_tradesARead-only
Analyze actual market transactions to understand market sentiment and liquidity.
Use this tool when you need to:
- Detect large trades that might signal institutional activity
- Calculate average trade size during specific periods
- Identify buy/sell pressure imbalances
- Monitor execution prices vs. order book prices
- Understand market momentum through trade flow
Trade data provides insights into actual market activity versus just orders,
helping you understand how other participants are behaving.
Example use cases:
- Detecting large "whale" transactions that might influence price
- Analyzing trade sizes to gauge market participation
- Identifying periods of aggressive buying or selling
- Understanding trade frequency as an indicator of market interest
- Comparing executed prices to orderbook mid-price for market impact analysis
Inputs: market_id (required), start_unix_ms (required), end_unix_ms (required).
paradex_vault_account_summaryARead-only
Get a comprehensive overview of a vault's trading account status.
Use this tool when you need to:
- Check account health and available margin
- Monitor total exposure and leverage
- Understand risk metrics and account status
- Assess trading capacity before placing new orders
- Get a consolidated view of account performance
This provides essential information about account standing and
trading capacity to inform risk management decisions.
Example use cases:
- Checking available margin before placing new orders
- Monitoring account health during market volatility
- Assessing total exposure across all markets
- Understanding maintenance margin requirements
- Planning position adjustments based on account metrics
Inputs: vault_address (required). Returns: result
paradex_vault_balanceARead-only
Get the current balance of a specific vault.
Retrieves the current balance information for a specific vault, including available funds, locked funds, and total balance. This is essential for understanding the financial state of a vault before executing trades or withdrawals.
Inputs: vault_address (required). Returns: result
paradex_vault_positionsARead-only
Monitor active trading positions to track performance and manage risk.
Use this tool when you need to:
- Get a complete view of all open positions for a vault
- Monitor unrealized P&L across all positions
- Check liquidation prices and margin requirements
- Assess position sizing and leverage across markets
- Track entry prices and position duration
Position monitoring is fundamental to risk management and provides
the necessary information for trade management decisions.
Example use cases:
- Checking the current status of all open trades
- Monitoring unrealized profit/loss across positions
- Assessing liquidation risk during market volatility
- Comparing performance across different markets
- Planning adjustments to position sizes or leverage
Inputs: vault_address (required). Returns: result
paradex_vaultsARead-only
Get detailed information about a specific vault or all vaults if no address is provided.
Retrieves comprehensive details about a specific vault identified by its address,
including configuration, permissions, and other vault-specific parameters.
Use jmespath_filter to reduce the number of results as much as possible as number of vaults can be large.
You can use JMESPath expressions to filter, sort, or limit the results.
Examples:
- Filter by owner: "[?owner_account=='0x123...']"
- Filter by status: "[?status=='ACTIVE']"
- Find vaults with specific strategy: "[?contains(strategies, 'strategy_id')]"
- Sort by creation date: "sort_by([*], &created_at)"
- Limit to newest vaults: "sort_by([*], &created_at)[-5:]"
- Select specific fields: "[*].{address: address, name: name, kind: kind, status: status}"
Inputs: vault_address, jmespath_filter, limit, offset.
paradex_vault_summaryARead-only
Get a comprehensive summary of a specific vault or all vaults if no address is provided.
Retrieves a summary of all important information about a vault,
including balance, positions, recent activity, and performance metrics.
This provides a high-level overview of the vault's current state.
Use jmespath_filter to reduce the number of results as much as possible as number of vaults can be large.
You can use JMESPath expressions to filter, sort, or transform the results.
Examples:
- Filter by TVL: "[?to_number(tvl) > `10000`]"
- Filter by performance: "[?to_number(total_roi) > `5.0`]"
- Sort by TVL (descending): "reverse(sort_by([*], &to_number(tvl)))"
- Get top performers: "sort_by([*], &to_number(total_roi))[-3:]"
- Filter by recent returns: "[?to_number(roi_24h) > `0.5`]"
- Extract specific metrics: "[*].{address: address, tvl: tvl, total_roi: total_roi, volume_24h: volume_24h}"
Inputs: vault_address, jmespath_filter, limit, offset.
paradex_vault_transfersARead-only
Track deposit and withdrawal history for auditing and reconciliation.
Use this tool when you need to:
- Verify deposits have completed and are available for trading
- Track withdrawal status and confirm transaction settlement
- Audit the complete fund flow history for a vault
- Reconcile on-chain transactions with platform records
- Understand historical capital allocation patterns
Complete transfer history is essential for proper accounting and provides
a clear audit trail of all capital movements.
Example use cases:
- Confirming that a recent deposit was credited to your account
- Tracking the status of pending withdrawals
- Creating transaction reports for accounting or tax purposes
- Verifying the total amount deposited over time
- Analyzing deposit/withdrawal patterns for strategy insights
Inputs: vault_address (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose. Market data tools (bbo, orderbook, klines, trades, markets, summaries, funding_data) cover different aspects. Vault tools (vault_account_summary, vault_balance, vault_positions, vaults, vault_summary, vault_transfers) each provide unique account information. System tools (system_config, system_state) and filters_model serve separate needs. No significant overlap.
All tool names follow the pattern 'paradex_' followed by a domain noun or compound noun (e.g., 'bbo', 'filters_model', 'vault_account_summary'). The naming structure is consistent, though some names use a single noun (e.g., 'paradex_markets') and others use multiple nouns (e.g., 'paradex_market_summaries'). This is a minor deviation from a strict pattern, but overall it is clear and predictable.
With 16 tools, the count is on the higher side for a data-oriented server, but each tool serves a distinct data retrieval purpose (market, system, vault). No tool seems superfluous. The number is appropriate for the scope of providing comprehensive read access to exchange data and account information.
The tool set is missing critical trading execution tools such as place_order, cancel_order, or modify_order. Given that the tools extensively support pre-trade analysis and account monitoring, the lack of order management creates a significant gap for actual trading. This suggests an incomplete surface for a server named 'Paradex Server'.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Trade Papertrade BTC and ETH perps from Claude, ChatGPT, Codex, Cursor and any MCP client.
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with cryptocurrency exchanges through CCXT, allowing for tasks like fetching balances, market data, creating orders, and trading operations in a standardized way.8MIT
- AlicenseAqualityNot gradedmaintenanceA bridge between AI assistants and the Paradex perpetual futures trading platform that enables retrieving market data, managing trading accounts, placing orders, and monitoring positions.26MIT
- AlicenseAqualityBmaintenanceA bridge between AI assistants and the Paradex perpetual futures trading platform for managing accounts, vaults, and orders. It enables users to retrieve real-time market data, monitor positions, and execute trading strategies through the Model Context Protocol.3333 PyPI2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for the Hyperliquid decentralized exchange, enabling AI assistants to perform trading operations, manage accounts, and retrieve market data.29 PyPI3MIT