mcp-tradovate

This MCP server provides a Tradovate integration for Claude Desktop, enabling an AI assistant to manage Tradovate trading accounts through natural language interactions. It exposes tools for authentication, account management, trading operations, and market data, allowing you to authenticate with Tradovate, view accounts and positions, manage risk settings, place and cancel orders, view fills, and fetch real-time or historical market data. Typical workflows include connecting to Tradovate via the authenticate tool, listing accounts with get_accounts, adjusting risk via set_risk_limits, submitting trades with place_order, and pulling live or historical market data with get_market_data and get_historical_data. The server is designed to work with Claude Desktop environments where these tools can be invoked by natural language prompts. To use it, ensure your Tradovate credentials are provided in the environment configuration and then run the server; the tools will be available to handle requests from your AI assistant.

Prerequisites:

• Go 1.18+ installed on your machine
• Git installed
• Tradovate developer credentials (username, password, app id/version, client id/secret)

Installation steps:

1. Clone the repository: git clone https://github.com/0xjmp/mcp-tradovate.git cd mcp-tradovate

2. Install dependencies and build: go mod download go build ./cmd/mcp-tradovate

3. Prepare environment variables (recommended): Create a .env file in the project root with Tradovate credentials: TRADOVATE_USERNAME=your_username TRADOVATE_PASSWORD=your_password TRADOVATE_APP_ID=your_app_id TRADOVATE_APP_VERSION=your_app_version TRADOVATE_CID=your_client_id TRADOVATE_SEC=your_client_secret

4. Run the server: ./mcp-tradovate

Notes:

• If you prefer not to run directly, you can use Go run without building: go run ./cmd/mcp-tradovate
• Ensure network access to Tradovate APIs and that credentials are kept secure.

Tips and common issues:

• Ensure your .env or environment variables are loaded before starting the server; the Tradovate client requires these credentials for authentication.
• If you encounter authentication failures, double-check credentials and that API access is enabled in Tradovate.
• For troubleshooting, verify internet connectivity, Tradovate API status, and that firewall rules allow outbound connections to Tradovate services.
• When deploying, consider using a secure secret management system for credentials and avoid committing .env files to version control.