Skip to main content
Glama
MarkHorwell

IG Integration MCP

by MarkHorwell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to IG Integration MCP

No user-submitted related servers found.

    Related Servers

    • IG Trading MCP

      MarkHorwell
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server for IG's REST Trading API, providing account/history, market data, position, working-order, and trade-confirmation tools with guarded OTC trade actions.
      20
      MIT

    • oanda-mcp

      florinel-chis
      A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      22
      1
      MIT

    • tastytrade-mcp

      bholzer
      F
      license
      A
      quality
      D
      maintenance
      MCP server for the tastytrade brokerage API, providing tools for account management, market data, and order execution.
      18
      -

    • ibkr-mcp

      jgalea
      A
      license
      B
      quality
      C
      maintenance
      A 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.
      15
      MIT

    • trading212-mcp

      florinel-chis
      A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      13
      1
      MIT

    • Avanza MCP

      Advance-xd
      A
      license
      Not graded
      quality
      C
      maintenance
      Local Streamable HTTP MCP server for Avanza that provides authentication, account data, instruments, market data, and order tools. Order tools can affect real money, so requires approval and safe configuration.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools map unambiguously to a resource and action, and the descriptions clearly distinguish OTC positions from working orders and streaming variants. However, ig_request overlaps with every specific endpoint and stream_ohlc_snapshot vs stream_updates could be confused, so it is not a perfect 5.

    Naming Consistency3/5

    The set mostly uses snake_case and commonly pairs verbs with resources for mutations, such as create_position, update_working_order, and close_position. Reads are inconsistent noun phrases like accounts, open_positions, and watchlists rather than list_* verbs, and ig_request, mutate_watchlist, and account_preferences break the action/resource pattern.

    Tool Count3/5

    22 tools is on the heavy side for an MCP surface, falling in the borderline 16-25 range. For a broad IG REST integration, each tool covers a meaningful capability, but the generic ig_request means the surface could be trimmed without losing much functionality.

    Completeness4/5

    The toolset covers the core trading lifecycle: positions, working orders, watchlists, account preferences, market data, sentiment, deal confirmations, and streaming. It lacks a dedicated transaction/closed-trade history tool and a get-working-order-by-ID equivalent, but ig_request provides a workaround for those gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources