MCPSERV.CLUB
DISHANK-PATEL

BrokerInbox MCP Server

MCP Server

AI‑driven email and trading workflows in one server

Active(75)
0stars
2views
Updated Apr 29, 2025

About

BrokerInbox integrates Gmail and Zerodha Kite Connect with AI agents, enabling natural‑language commands to read, send, delete emails and place trades or fetch market data. It exposes these actions as HTTP endpoints for LLM orchestration.

Capabilities

Resources
Access data sources
Tools
Execute functions
Prompts
Pre-built templates
Sampling
AI model interactions

BrokerInbox MCP Server Workflow

BrokerInbox is a purpose‑built MCP server that bridges the gap between conversational AI assistants and two of the most frequently used productivity APIs: Gmail for communication and Zerodha’s Kite Connect for trading. By exposing a unified set of HTTP endpoints that map directly to natural‑language actions, it allows agents such as Claude or Cursor to manage email and execute trades without writing any custom code. This eliminates the friction of handling OAuth flows, API rate limits, and data parsing, enabling developers to focus on higher‑level business logic.

At its core, BrokerInbox offers a two‑fold integration. The Gmail module supports the full lifecycle of an email—searching, reading, replying, and deleting—while also providing analytical hooks like sentiment scoring, keyword extraction, and summarization. The Zerodha module gives agents the ability to place market or limit orders, retrieve holdings and positions, and pull real‑time price data (LTP, OHLC). Both modules are wrapped in a consistent API contract that the MCP client can invoke via simple JSON payloads, making the server agnostic to the underlying SDKs.

The value proposition extends beyond raw API calls. BrokerInbox includes an orchestration layer that routes natural‑language prompts to the appropriate tool based on intent recognition. Developers can chain complex workflows using optional LangChain or OpenAI Functions, turning a single user request into a multi‑step process—such as “send an email to my manager summarizing the day’s trades and then place a limit order for XYZ.” The server also manages session persistence, storing OAuth tokens and trade logs so that repeat interactions remain authenticated without user intervention.

Typical use cases span personal productivity, fintech services, and automated trading bots. A portfolio manager can ask an assistant to “check my inbox for any trade confirmations, summarize them, and update my risk dashboard.” A retail trader might instruct the assistant to “buy 50 shares of ABC at market price, then email me a confirmation.” Because the MCP server abstracts authentication and API quirks, these scenarios become straightforward conversational commands rather than complex scripts.

Unique advantages of BrokerInbox include its dual‑domain focus, built‑in analytical capabilities, and seamless integration with LLM orchestration frameworks. For developers building AI‑powered workflows that require both communication and market interaction, BrokerInbox provides a ready‑to‑use bridge that accelerates prototyping and reduces maintenance overhead.