In-depth architectural comparison of the IBKR Portfolio Builder and Claude Task Master 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
IBKR Portfolio Builder
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Claude Task Master
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Verdict Summary: Choose IBKR Portfolio Builder if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Claude Task Master if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose IBKR Portfolio Builder when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
AI-powered task management system for AI-driven development. Features PRD parsing, task expansion, multi-provider support (Claude, OpenAI, Gemini, Perplexity, xAI), and selective tool loading for optimized context usage.
IBKR Portfolio Builder is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Claude Task Master belongs to Developer Tools using local stdio subprocess. Select IBKR Portfolio Builder when you need capabilities focused on developer tools and Claude Task Master when you require tools for developer tools.
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.