IG Trading MCP
Related Servers
Alternatives to IG Trading MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server for IG's REST Trading API and Lightstreamer streaming API. Provides tools for accounts, markets, positions, orders, watchlists, sentiment, OTC trades, and streaming price/account/trade/chart data.22Apache 2.0
- AlicenseBqualityCmaintenanceA read-only-by-default MCP server for Interactive Brokers that exposes account, positions, PnL, market data, and trade history from a local TWS/IB Gateway session, with optional trading capabilities.15MIT
- AlicenseAqualityBmaintenanceMCP server for the Oanda v20 REST API enabling forex/CFD trading account management, market data retrieval, and order/trade operations with a read-first design and practice environment by default.221MIT
- AlicenseAqualityBmaintenanceMCP server for the Trading 212 public API, enabling account, portfolio, order, pie, and history access with read tools always available and trading tools opt-in.131MIT
- FlicenseBqualityDmaintenanceMCP server for Interactive Brokers via IB Gateway, enabling read access to account data and trading capabilities for paper accounts.11-
- AlicenseAqualityCmaintenanceExtensible trading-intelligence MCP server with diagnostic tools, structured logging, and tool registration; currently provides server info tool with plans for market data adapters.17 npm-
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action, with clear separation between positions, working orders, market data, and account history. Even similar-sounding tools like get_activity and get_transactions are differentiated by their descriptions (account activity vs. financial transactions).
All tools follow the ig_ prefix followed by a consistent verb_noun pattern (e.g., list_positions, get_market, create_position, cancel_working_order). The naming is uniform and predictable.
20 tools is a bit above the typical 3-15 range, but the breadth of the IG trading domain (accounts, markets, positions, working orders, history) justifies the count. Each tool serves a distinct purpose with no redundancy.
The tool set covers the full lifecycle for positions (create, get, list, update, close) and working orders (create, list, update, cancel), plus market data and account history. There are no obvious dead ends; operations like get_deal_confirmation support post-submission workflows.