Layer II · Connectivity
No supported-broker list to be missing from.
Every platform in this category ships a list of supported venues, and yours is on it or you wait. QuantIDE ships the layer beneath that list. Adapters are written against your broker’s and your data vendor’s own APIs, as code in your project, with your keys on your disk.
What it holds
Anything with an API. Adapters are written against your broker and data sources, with credentials kept local.
01The adapter is authored, not awaited
Describe the venue and an adapter is written against its API as a Model Context Protocol server in your project. You can read it, fix it, version it, and keep it if you ever leave.
02Credentials stay local
Broker and data keys live on your machine and never travel when a workspace is shared. They are not held by us to make anything run.
03Servers you already run
The client speaks standard MCP: connect an existing server, list its tools and call them. Anything that already exposes an MCP interface works without being rewritten.
04Order routing, built deliberately
Nothing trades live out of the box. Routing orders is something you build here against your venue, with your credentials, and test before it touches capital.
Broker adapters · Data feeds · FIX & REST · MCP servers
Due diligence
Questions asked first.
So does QuantIDE support Interactive Brokers?
Not as a pre-built integration, and we will not claim otherwise. What ships is the layer that lets an IBKR adapter be written against their API in your project. The result is yours.
What happens to my adapters if I cancel?
They are files in your repository. They do not phone home and they do not stop working.