EZIB-MCP: Interactive Brokers Trading for AI Agents

Created By
kelvingaoa year ago
MCP server built on ezib_async that exposes Interactive Brokers' trading and market data functionality.
Overview

what is EZIB-MCP?

EZIB-MCP is an implementation of the Model Context Protocol (MCP) server that allows AI agents to interact with Interactive Brokers' trading platform, providing access to market data, account information, and trading functionalities.

how to use EZIB-MCP?

To use EZIB-MCP, clone the repository, install the dependencies, configure your environment variables, and run the server either using pip or Docker. You can then connect your AI agents to the server to perform trading operations.

key features of EZIB-MCP?

  • Access to account balances, positions, and portfolio data.
  • Retrieve real-time and historical market data.
  • Place, modify, and cancel orders.
  • Monitor and manage trading positions.

use cases of EZIB-MCP?

  1. Algorithmic trading with AI agents.
  2. Real-time market analysis and data retrieval.
  3. Automated order management and execution.

FAQ from EZIB-MCP?

  • What is required to run EZIB-MCP?

You need Python 3.11+, Interactive Brokers TWS or IB Gateway, and optionally Docker for containerized deployment.

  • Can I use EZIB-MCP for live trading?

Yes, EZIB-MCP can be used for live trading with Interactive Brokers.

  • Is there a license for EZIB-MCP?

Yes, EZIB-MCP is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kelvingao
Star
0
Language
Python
License
MIT license
Category
finance

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago