tradovate
Tradovate MCP Server
claude mcp add --transport stdio alexanimal-tradovate-mcp-server npm start \ --env TRADOVATE_CID="Client ID" \ --env TRADOVATE_SEC="Client secret" \ --env TRADOVATE_APP_ID="Aplicaton ID (e.g., Sample App)" \ --env TRADOVATE_PASSWORD="Tradovate account password" \ --env TRADOVATE_USERNAME="Tradoate account username" \ --env TRADOVATE_APP_VERSION="Application version (e.g., 1.0)" \ --env TRADOVATE_API_ENVIRONMENT="demo environment (e.g., demo or production)"
How to use
This MCP server exposes a set of tools to interact with the Tradovate API through a standardized Model Context Protocol interface. It includes capabilities to fetch contract details, list and manage positions, place and modify orders, cancel orders, liquidate positions, and retrieve account summaries, as well as obtaining live market data such as quotes, DOM, and chart data. You can access these tools via the MCP endpoints and invoke them with the appropriate parameters (e.g., symbol for contract details, accountId for positions, order parameters for placing orders). The server also supports fallback to simulated data when the Tradovate API is unavailable, ensuring continued responses for MCP workflows and testing. Typical usage involves starting the server, authenticating with the Tradovate API, and then issuing tool requests (e.g., get_contract_details, list_positions, place_order) through your MCP client or inspector tool to manage trading activities programmatically.
How to install
Prerequisites:
- Node.js and npm installed
- Access to Tradovate API credentials
Installation steps:
-
Clone the repository git clone https://github.com/alexanimal/tradovate-mcp-server.git cd tradovate-mcp-server
-
Install dependencies npm install
-
Create a .env file with Tradovate credentials TRADOVATE_API_ENVIRONMENT=demo TRADOVATE_USERNAME=your_username TRADOVATE_PASSWORD=your_password TRADOVATE_APP_ID=Sample App TRADOVATE_APP_VERSION=1.0 TRADOVATE_CID=your_cid TRADOVATE_SEC=your_sec
-
Start the server npm start
Optional for development and testing:
- Run inspector tool if provided npm run inspector
- Build and test (if you customize locally) npm run build npm test
Additional notes
Notes and tips:
- Ensure your Tradovate credentials are valid and have API access.
- If API calls fail, the server will fall back to simulated data; this is useful for development and MCP workflow testing.
- Environment variables in .env or the MCP deployment environment should be kept secure and not exposed in public repos.
- The available tools include: get_contract_details, list_positions, place_order, modify_order, cancel_order, liquidate_position, get_account_summary, and get_market_data.
- If you need to customize endpoints or data caching behavior, modify the src files (e.g., src/data.ts, src/tools.ts) and rebuild.
- When deploying, consider setting a proper environment for TRADOVATE_API_ENVIRONMENT (e.g., production) and ensuring credentials are rotated periodically.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.