IBI Portfolio MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IBI_DEMO | No | 1 returns a made-up portfolio, no IBI login. For trying it out. | 0 |
| IBI_PASS | No | IBI password (default: secure vault). | |
| IBI_USER | No | IBI username (default: secure vault). | |
| IBI_HEADED | No | 1 shows the browser window (needed for SMS codes). | 0 |
| IBI_ENV_FILE | No | Extra env file to load. | ./.env |
| IBI_PASS_CMD | No | Command that prints the IBI password (default: secure vault). | |
| IBI_USER_CMD | No | Command that prints the IBI username (default: secure vault). | |
| IBI_DEBUG_DIR | No | Saves screenshots and raw JSON there. They contain your balances: delete them when done. | |
| IBI_CACHE_SECONDS | No | Reuse the last read for this long, so one chat does not log in again and again. | 300 |
| IBI_LOGIN_TIMEOUT_S | No | How long to wait for login. Default is 90 seconds, or 180 seconds when IBI_HEADED=1. | 90 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_portfolioA | Current IBI portfolio: total value, cash, profit/loss, and every open position (symbol, quantity, cost, market value, P/L, weight). Values come from IBI itself, in USD. Set refresh=true to skip the short cache. |
| get_account_activityC | Recent orders and executions from IBI's 'Latest Account Activity' (side, symbol, status, quantity, price, fees, dates). Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools target clearly distinct resources: portfolio holdings/value versus account activity/executions. There is little risk of confusing one for the other.
Both tools follow a consistent get_<resource> pattern. The naming is predictable and readable.
Two tools is quite thin for a portfolio-oriented server, even if the scope is intentionally read-only. It covers two key views but leaves little room for additional portfolio operations.
The surface covers portfolio summary and recent activity, but omits common operations such as per-position lookup, performance history, or order placement. As a read-only monitor it is useful but notably incomplete.