Agent Plugins Marketplace
← All plugins

trading-broker-integration

v2.1.0

Broker integration for algorithmic trading in Python: Interactive Brokers via the TWS API and ib_async across equities, options, futures, FX, CFDs and crypto (per-class contracts and market rules, order types and TIF/fill-mode capability resolution, brackets in depth, a classified catalog of all 458 published TWS message codes, venue-behaviour verification tooling, reconnection resilience, deployment on Windows, Linux, macOS and Docker), MetaTrader 5 via the official synchronous API (polling-based event systems, order execution with fill modes, historical data, the aiomql async framework, a ZeroMQ bridge, Windows production deployment), and the vendor-neutral vocabulary shared between them: five access archetypes, the single-broker/multi-broker-platform axis, a reference order-lifecycle state machine, session and recovery patterns, and a six-rank evidence ladder with provenance tags for what a claim about a venue is worth

Claude Code3 Skills

By Alfio CaprinoLicense: MIT8 GitHub starsUpdated 4 hours ago

Directory evidence

Runtimes
Claude Code
Parsed components
3 skill or MCP entries
Source updated
Aug 26, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install plugin

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install trading-broker-integration@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/acaprino/daodan

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is exports/claude/plugins/trading-broker-integration/.

Plugin files

exports/claude/plugins/trading-broker-integration/
├── .claude-plugin/plugin.json
├── skills/broker-vocabulary/SKILL.md
├── skills/ibkr/SKILL.md
└── skills/mt5/SKILL.md

Included Skills3

broker-vocabularyskills/broker-vocabulary/SKILL.md

Vendor-neutral vocabulary for programmatic broker integration: the five access archetypes, the second axis separating a single broker from a multi-broker platform, the reference order state machine, session and recovery, and the evidence ladder that decides what a claim about a venue is worth. TRIGGER WHEN: comparing brokers or integration paths, starting an integration against a broker with no dedicated plugin, or naming what kind of access path a system uses. DO NOT TRIGGER WHEN: the question is about one specific broker that has its own plugin, or about strategy, backtesting, or portfolio construction.

ibkrskills/ibkr/SKILL.md

Authoritative reference for Interactive Brokers integration in Python, across every asset class, with tooling to verify venue behaviour against a paper Gateway instead of guessing. TRIGGER WHEN: building, auditing or debugging anything that talks to TWS or IB Gateway via the TWS API and ib_async: contracts, market data, orders, brackets, error codes, reconnection, deployment, or a question about how IBKR actually behaves. DO NOT TRIGGER WHEN: MetaTrader 5 (use mt5), or the IBKR Web API with no TWS connection.

mt5skills/mt5/SKILL.md

Knowledge base for the official API, its polling model, and Windows-side production concerns. TRIGGER WHEN: building, implementing, writing, coding, creating, optimizing, or debugging MT5 or MetaTrader 5 trading systems with Python, including the aiomql and ZeroMQ bridge alternatives. DO NOT TRIGGER WHEN: the broker is Interactive Brokers (use ibkr), or the question is about strategy design rather than the terminal and its API.

Plugin manifests1

exports/claude/plugins/trading-broker-integration/.claude-plugin/plugin.json
{
  "author": {
    "name": "Alfio Caprino"
  },
  "description": "Broker integration for algorithmic trading in Python: Interactive Brokers via the TWS API and ib_async across equities, options, futures, FX, CFDs and crypto (per-class contracts and market rules, order types and TIF/fill-mode capability resolution, brackets in depth, a classified catalog of all 458 published TWS message codes, venue-behaviour verification tooling, reconnection resilience, deployment on Windows, Linux, macOS and Docker), MetaTrader 5 via the official synchronous API (polling-based event systems, order execution with fill modes, historical data, the aiomql async framework, a ZeroMQ bridge, Windows production deployment), and the vendor-neutral vocabulary shared between them: five access archetypes, the single-broker/multi-broker-platform axis, a reference order-lifecycle state machine, session and recovery patterns, and a six-rank evidence ladder with provenance tags for what a claim about a venue is worth",
  "license": "MIT",
  "name": "trading-broker-integration",
  "version": "2.1.0"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[trading-broker-integration on Agent Plugins Marketplace](https://pluginsmp.com/plugins/trading-broker-integration)