4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
IBKR (Interactive Brokers) MCP Server

Bring Trading
to CrewAI

Learn how to connect IBKR (Interactive Brokers) to CrewAI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Cancel OrderGet Account SummaryGet Flex StatementGet Market Data SnapshotGet Portfolio LedgerModify OrderPlace OrderSend Flex RequestTickle Session

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
IBKR (Interactive Brokers)

What is the IBKR (Interactive Brokers) MCP Server?

Connect your Interactive Brokers account to any AI agent to automate your trading workflows and portfolio monitoring through the Client Portal API.

What you can do

  • Order Management — Place, modify, and cancel orders for specific accounts using natural language commands.
  • Market Data — Fetch real-time snapshots for specific contracts (ConIds) to inform your trading decisions.
  • Portfolio Tracking — Monitor cash balances by currency and view comprehensive account summaries including equity and margin metrics.
  • Advanced Reporting — Programmatically request and retrieve pre-configured Flex Query reports for deep financial analysis and auditing.
  • Session Maintenance — Keep your API session active with built-in session management tools.

How it works

  1. Subscribe to this server
  2. Enter your IBKR Client Portal API URL and your optional Flex Web Service Token
  3. Start managing your brokerage account from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Active Traders — execute and modify orders quickly without switching between complex trading interfaces
  • Financial Analysts — automate the retrieval of portfolio ledgers and Flex statements for reporting
  • Developers — integrate real-time market data and account management directly into your coding environment

Built-in capabilities (9)

cancel_order

Cancel an existing order

get_account_summary

Get account summary

get_flex_statement

Retrieve a generated Flex Query report

get_market_data_snapshot

Get market data snapshot for contracts

get_portfolio_ledger

Get portfolio ledger

modify_order

Modify an existing order

place_order

Requires a JSON array of order objects. Place a new order

send_flex_request

Returns a ReferenceCode to be used with get_flex_statement. Generate a Flex Query report

tickle_session

Maintain Client Portal API session

Why CrewAI?

When paired with CrewAI, IBKR (Interactive Brokers) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call IBKR (Interactive Brokers) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

IBKR (Interactive Brokers) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

IBKR (Interactive Brokers) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect IBKR (Interactive Brokers) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for IBKR (Interactive Brokers) in CrewAI

The IBKR (Interactive Brokers) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

IBKR (Interactive Brokers)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures IBKR (Interactive Brokers) for CrewAI

Every tool call from CrewAI to the IBKR (Interactive Brokers) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I prevent my IBKR API session from timing out?

You can use the tickle_session tool. It is designed to maintain the Client Portal API session by sending a heartbeat, preventing timeouts due to inactivity.

02

Can I retrieve historical trade reports through this server?

Yes. First, use send_flex_request with your Flex Query ID to generate a report. Then, use the returned Reference Code with get_flex_statement to download the data.

03

How do I check my current buying power and margin requirements?

Use the get_account_summary tool with your Account ID. It returns a comprehensive summary of equity, margin, and other key financial metrics for the specified account.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →