ibkr-mcp-guard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLUGIN_DATA | No | Data directory (set by plugin hosts). Otherwise $XDG_CONFIG_HOME/ibkr-mcp-guard or ~/.config/ibkr-mcp-guard. | |
| CLAUDE_PLUGIN_DATA | No | Data directory (set by plugin hosts). Otherwise $XDG_CONFIG_HOME/ibkr-mcp-guard or ~/.config/ibkr-mcp-guard. | |
| IBKR_MCP_GUARD_PAPER | No | Set to 1 to enable paper trading mode: order submission to IBKR paper accounts only. | |
| IBKR_MCP_GUARD_STORE | No | Set to file to use the 0600 file instead of the macOS Keychain. | |
| IBKR_MCP_GUARD_READONLY | No | Set to 1 to hide and refuse write and draft tools; reads only. Also turns paper mode off. | |
| IBKR_MCP_GUARD_UPSTREAM | No | Testing only: a different upstream MCP URL. A warning is logged to stderr. | |
| IBKR_MCP_GUARD_NO_BROWSER | No | Set to 1 to not open a browser; the sign-in result includes the link to open yourself (useful over SSH). | |
| IBKR_MCP_GUARD_PAPER_NO_CONFIRM | No | Set to 1 in paper mode to skip the guard's Approve/Cancel prompt before each paper order (for automated strategy runs). Has no effect outside paper mode. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ibkr_sign_inA | Start signing in to Interactive Brokers in the user's browser (read + order-draft access only; order submission is never requested). Returns immediately; the user approves in the browser and then asks again. |
| ibkr_statusA | Show whether the user is signed in to Interactive Brokers, the account ids, granted scopes, token expiry, and confirm that order submission was not granted. |
| ibkr_sign_outA | Sign out of Interactive Brokers: revoke the tokens at IBKR and delete them from this computer. |
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 3 tools
The three tools map cleanly to distinct authentication lifecycle actions: sign in, inspect status, and sign out. There is no overlap in purpose, and the descriptions make the boundaries clear.
All tools use the same predictable prefix and verb pattern: ibkr_sign_in, ibkr_status, ibkr_sign_out. The convention is consistent and readable.
For an authentication/guard server, three tools are sufficient and each earns its place. There are no redundant or filler tools.
The server covers the full auth lifecycle: sign in, check current status and scopes, and sign out/revoke tokens. No obvious operations are missing for its stated purpose as a guard around IBKR access.