MCP Paradex Server
# 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.
<a href="https://glama.ai/mcp/servers/cq4bz5ljqj">
<img width="380" height="200" src="https://glama.ai/mcp/servers/cq4bz5ljqj/badge" alt="Paradex Server MCP server" />
</a>
## 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
## Prerequisites
- Python 3.10+
## Installation
### Quick Start
#### Cursor IDE
Click to automatically configure this MCP server in Cursor:
[](https://cursor.com/install-mcp?name=paradex&config=eyJjb21tYW5kIjoidXZ4IiwiYXJncyI6WyJtY3AtcGFyYWRleCJdLCJlbnYiOnsiUEFSQURFWF9FTlZJUk9OTUVOVCI6InRlc3RuZXQiLCJQQVJBREVYX0FDQ09VTlRfUFJJVkFURV9LRVkiOiJ5b3VyX3ByaXZhdGVfa2V5In19Cg%3D%3D)
#### Claude Code CLI
```bash
claude mcp add paradex uvx mcp-paradex
```
#### Smithery (Claude Desktop)
```bash
npx -y @smithery/cli install @sv/mcp-paradex-py --client claude
```
### Standard Installation
#### PyPI
```bash
pip install mcp-paradex
```
#### uvx (Recommended)
```bash
uvx mcp-paradex
```
### Development Setup
1. Clone the repository:
```bash
git clone https://github.com/sv/mcp-paradex-py.git
cd mcp-paradex-py
```
2. Install development dependencies:
```bash
uv sync --dev --all-extras
```
3. Run locally:
```bash
uv run mcp-paradex
```
## Configuration
### Environment Variables
Set these environment variables for authentication:
- `PARADEX_ENVIRONMENT`: Set to `prod`, `testnet`, or `nightly` (default: `prod`)
- `PARADEX_ACCOUNT_PRIVATE_KEY`: Your Paradex account private key
### Using .env File
```bash
cp .env.template .env
# Edit .env with your credentials
```
### Client Configuration
#### Claude Desktop
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"paradex": {
"command": "uvx",
"args": ["mcp-paradex"],
"env": {
"PARADEX_ENVIRONMENT": "testnet",
"PARADEX_ACCOUNT_PRIVATE_KEY": "your_private_key"
}
}
}
}
```
#### Docker (local / stdio)
```bash
# 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-py
```
#### Docker (AWS Lambda / HTTP)
Use `Dockerfile.aws` for remote deployments via AWS Lambda with the
[Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter).
The adapter bridges Lambda invocations to the server's HTTP endpoint,
so no Lambda-specific code is needed.
```bash
# 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-aws
```
The server will be available at `http://localhost:8080/mcp`.
**Deploying to Lambda:**
1. Push the image to ECR
2. Create a Lambda function from the container image
3. Set the Lambda Function URL invoke mode to `RESPONSE_STREAM`
4. Set environment variables on the Lambda function:
- `MCP_TRANSPORT=streamable-http`
- `MCP_STATELESS=true`
- `PARADEX_ENVIRONMENT=prod` (or `testnet`)
- `PARADEX_ACCOUNT_PRIVATE_KEY=your_key` (optional, for trading)
## Available Resources and Tools
### Resources
#### System Resources
- `paradex://system/config` - Get Paradex system configuration
- `paradex://system/time` - Get current system time
- `paradex://system/state` - Get system operational state
#### Market Resources
- `paradex://markets` - List of available markets
- `paradex://market/summary/{market_id}` - Detailed market information
#### Vault Resources
- `paradex://vaults` - List all vaults
- `paradex://vaults/config` - Global vault configuration
- `paradex://vaults/balance/{vault_id}` - Vault balance
- `paradex://vaults/summary/{vault_id}` - Comprehensive vault summary
- `paradex://vaults/transfers/{vault_id}` - Deposit/withdrawal history
- `paradex://vaults/positions/{vault_id}` - Current trading positions
- `paradex://vaults/account-summary/{vault_id}` - Trading account information
### Tools
#### System Tools
- `paradex_system_config` - Get global system configuration
- `paradex_system_state` - Get current system state
#### Market Tools
- `paradex_markets` - Get detailed market information
- `paradex_market_summaries` - Get market summaries with metrics
- `paradex_funding_data` - Get historical funding rate data
- `paradex_orderbook` - Get current orderbook with customizable depth
- `paradex_klines` - Get historical candlestick data
- `paradex_trades` - Get recent trades
- `paradex_bbo` - Get best bid and offer
#### Account Tools
- `paradex_account_summary` - Get account summary
- `paradex_account_positions` - Get current positions
- `paradex_account_fills` - Get trade fills
- `paradex_account_funding_payments` - Get funding payments
- `paradex_account_transactions` - Get transaction history
#### Order Tools
- `paradex_open_orders` - Get all open orders
- `paradex_create_order` - Create new order
- `paradex_cancel_orders` - Cancel existing orders
- `paradex_order_status` - Get order status
- `paradex_orders_history` - Get historical orders
#### Vault Tools
- `paradex_vaults` - Get detailed vault information
- `paradex_vaults_config` - Get global vault configuration
- `paradex_vault_balance` - Get vault balance
- `paradex_vault_summary` - Get comprehensive vault summary
- `paradex_vault_transfers` - Get deposit/withdrawal history
- `paradex_vault_positions` - Get current vault positions
- `paradex_vault_account_summary` - Get vault trading account info
## Trading Analysis Prompts
### Market Analysis
- `market_overview` - Comprehensive crypto market overview
- `market_analysis` - Detailed technical and microstructure analysis
### Position and Portfolio Management
- `position_management` - Comprehensive position analysis
- `create_optimal_order` - Design optimal order parameters
- `hedging_strategy` - Develop effective hedging strategies
- `portfolio_risk_assessment` - Thorough portfolio risk analysis
- `liquidation_protection` - Identify and mitigate liquidation risks
### Investment Strategies
- `vault_analysis` - Comprehensive vault analysis for investment decisions
- `funding_rate_opportunity` - Identify funding rate arbitrage opportunities
- `trading_consultation` - Interactive trading advice and consultation
## Documentation MCP
Enhanced results with Paradex documentation access:
```json
"paradex-docs-mcp": {
"command": "uvx",
"args": [
"--from",
"mcpdoc",
"mcpdoc",
"--urls",
"Paradex:https://docs.paradex.trade/llms.txt",
"--transport",
"stdio"
]
}
```
## Contributing
Please see [CONTRIBUTING.md](CONTRIBUTING.md) for information on how to
contribute to this project, development setup, and our coding standards.
## License
[MIT License](LICENSE)
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'.