In-depth architectural comparison of the MCP Server Docker and IBKR Portfolio Builder MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Server Docker
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
IBKR Portfolio Builder
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Server Docker if you need specialized Developer Tools tools running via a local process. Choose IBKR Portfolio Builder if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Server Docker when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP Server Docker is categorized under Developer Tools and uses a local stdio subprocess. In contrast, IBKR Portfolio Builder belongs to Developer Tools using remote streaming HTTP/SSE transport. Select MCP Server Docker when you need capabilities focused on developer tools and IBKR Portfolio Builder when you require tools for developer tools.
NetLiquidation / BuyingPower / TotalCashValue / AvailableFunds / UnrealizedPnL for the connected paper or live account.
ib_positions
Open positions across managed accounts, with quantity / avg cost / mark-to-market / unrealized PnL.
ib_open_orders
Currently working orders with status, filled / remaining quantity, average fill price.
ib_trades
Recent executed fills (`days_back` window, IBKR caps history ~7 days).
ib_price_snapshot
Current bid / ask / last / high / low / volume for a US stock. Surfaces IBKR market-data restriction messages clearly.
ib_price_history
OHLCV bars for any duration / bar size (`1 day`, `1 hour`, `5 mins`, ...). Always works regardless of market-data subscription.
ib_search_contracts
Fuzzy-search IBKR's contract database by name / partial ticker.
ib_contract_details
Full contract metadata — `long_name`, `industry`, `category`, `subcategory`, trading hours, valid exchanges. **The hook for sector-aware top-down screening.
ib_scan_catalog
The typed scan catalog. Filter by `category`, `strategy`, `instrument`, free-text `query`; optionally return the full list of available categories + strategies via `list_meta=true`.
ib_filter_catalog
Filter parameter codes grouped by category (`price`, `volume`, `market_cap`, `fundamentals`, `technical`, `options`), with an instrument applicability note.
ib_screener_codes
Substring search over the raw `scan-parameters.xml` codes (legacy / fallback). Useful for newer vendor codes not yet in the curated catalog.
ib_screener
Run an IBKR scan — pass `scan_code`, `instrument`, `location`, optional price / volume filters. Returns rank + ticker + exchange.