R
rcontesti/IB_MCP
Market data and orders through the Interactive Brokers API
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- 来源明细
- 收录自 abordage/awesome-mcp 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
我们收录于 2026-11-05;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
> [!Note]
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
> #### Project Status
> This project is currently under active development. Features may be incomplete, and breaking changes may occur.
## Motivation
This project is built exclusively on the Interactive Brokers Web API, and this is a deliberate design choice. While the TWS API is powerful, the Web API provides a more modern and flexible foundation for the goals of this project.
### TWS API MCP vs. WEB API MCP?
Why not using the TWS API? The short answer is that the WEB API is planned to be more comprehensive. By more comprehensive I mean, it brings account management, specifically reporting, into the same place. The two other important reasons are: 1. The Web API is standalone. It does not require you to run the TWS desktop software or IB Gateway. 2. Model context protocols (MCPs) are easier to build on top of HTTPS communication rather than TCP/IP sockets.
If it is more comprehensive why not using just the WEB API? Three reasons: 1. WEB API is in beta (see Limitations) 2. TWS is faster and more reliable for trading. 3. TWS has some trading functionalities that the WEB API does not have.
While other projects act as a "bridge" to make the TWS API look like a web API, they introduce an unofficial, third-party dependency. This project avoids that risk by using the official IBKR Web API directly, ensuring better long-term stability and support.
In summary:
If you need fast and reliable trading go with TWS API
If you need a more comprehensive and cloud ready solution go with the WEB API
For a more detailed, side-by-side breakdown, please see the TWS vs. Web API Comparison section.
## Table of Contents
Table of Contents
Overview
Docker Desktop Setup
Limitations of Multi-Container Setup
Session Management
Future Work
Endpoints Status
TWS vs WEB comparison
Limitations
Architecture
📦 Interactive Brokers Client Portal Gateway Docker Container
🔧 What This Container Does
[📦 Interactive Brokers Routers Generator Docker Container \[WIP\]](#-interactive-brokers-routers-generator-docker-container-wip)
📦 IB MCP Server Docker Container
🔧 What This Container Does
References
Contributing
License
## Overview
This project provides an Interactive Brokers (IB) API interface using the Model Context Protocol (MCP). There are several ways to interact with Interactive Brokers, like the TWS API, the WEB API, Excel RTD and FIX among others. This project is built on top of Interactive Brokers WEB API.
This development uses the retail authentication process which is managed using the Client Portal Gateway, a small Java program used to route local web requests with appropriate authentication.
## Docker Desktop Setup
See a quick walkthrough in YOUTUBE
1. Clone the repo, set env variables and build the images
bash
# Clone the repository
git clone https://github.com/rcontesti/IBMCP.git
# Navigate to the project directory
cd IBMCP
# Copy the .env.example file to .env and edit as needed
cp .env.example .env
# Build the image
docker compose up --build -d
2. Auth with your IB account and credentials to:
After the image is up and running, navigate to https://{GATEWAYBASEURL}:{GATEWAYPORT} (e.g.: https://localhost:5055/) to login.
You will also find the login path in the logs of the API gateway container:
> This project is currently under active development. Features may be incomplete, and breaking changes may occur.
## Motivation
This project is built exclusively on the Interactive Brokers Web API, and this is a deliberate design choice. While the TWS API is powerful, the Web API provides a more modern and flexible foundation for the goals of this project.
### TWS API MCP vs. WEB API MCP?
Why not using the TWS API? The short answer is that the WEB API is planned to be more comprehensive. By more comprehensive I mean, it brings account management, specifically reporting, into the same place. The two other important reasons are: 1. The Web API is standalone. It does not require you to run the TWS desktop software or IB Gateway. 2. Model context protocols (MCPs) are easier to build on top of HTTPS communication rather than TCP/IP sockets.
If it is more comprehensive why not using just the WEB API? Three reasons: 1. WEB API is in beta (see Limitations) 2. TWS is faster and more reliable for trading. 3. TWS has some trading functionalities that the WEB API does not have.
While other projects act as a "bridge" to make the TWS API look like a web API, they introduce an unofficial, third-party dependency. This project avoids that risk by using the official IBKR Web API directly, ensuring better long-term stability and support.
In summary:
If you need fast and reliable trading go with TWS API
If you need a more comprehensive and cloud ready solution go with the WEB API
For a more detailed, side-by-side breakdown, please see the TWS vs. Web API Comparison section.
## Table of Contents
Table of Contents
Overview
Docker Desktop Setup
Limitations of Multi-Container Setup
Session Management
Future Work
Endpoints Status
TWS vs WEB comparison
Limitations
Architecture
📦 Interactive Brokers Client Portal Gateway Docker Container
🔧 What This Container Does
[📦 Interactive Brokers Routers Generator Docker Container \[WIP\]](#-interactive-brokers-routers-generator-docker-container-wip)
📦 IB MCP Server Docker Container
🔧 What This Container Does
References
Contributing
License
## Overview
This project provides an Interactive Brokers (IB) API interface using the Model Context Protocol (MCP). There are several ways to interact with Interactive Brokers, like the TWS API, the WEB API, Excel RTD and FIX among others. This project is built on top of Interactive Brokers WEB API.
This development uses the retail authentication process which is managed using the Client Portal Gateway, a small Java program used to route local web requests with appropriate authentication.
## Docker Desktop Setup
See a quick walkthrough in YOUTUBE
1. Clone the repo, set env variables and build the images
bash
# Clone the repository
git clone https://github.com/rcontesti/IBMCP.git
# Navigate to the project directory
cd IBMCP
# Copy the .env.example file to .env and edit as needed
cp .env.example .env
# Build the image
docker compose up --build -d
2. Auth with your IB account and credentials to:
After the image is up and running, navigate to https://{GATEWAYBASEURL}:{GATEWAYPORT} (e.g.: https://localhost:5055/) to login.
You will also find the login path in the logs of the API gateway container:
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/rcontesti-ib-mcp/)
- 来源
- awesome · https://github.com/rcontesti/IB_MCP
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。