A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
6 ★ · aranjan/kite-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 6 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository aranjan/kite-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
MCP server for Zerodha Kite -- trade Indian stocks through natural conversation with any MCP-compatible AI assistant. Why an MCP server instead of a Python library? Traditional Kite wrappers require you to write Python code to trade. With kite-mcp, you just talk: No code. No scripts. No terminal. Just conversation. kite-mcp connects any MCP-compatible AI assistant directly to your Zerodha account with 14 trading tools, automated TOTP login, and auto-retry on expired tokens. How it works Your AI assistant interprets your intent, maps stock names to symbols (e.g., "Infosys" to NSE:INFY), checks your funds, and executes trades -- all through the MCP protocol. The server handles authentication automatically, including daily token refresh via TOTP. Features 14 tools for complete trading control: | Tool | Description | |------|-------------| | kite_login | Auto-authenticate with TOTP | | get_holdings | Portfolio holdings with P&L | | get_positions | Today's intraday/delivery positions | | get_orders | Today's order history | | get_margins | Available funds and margins | | get_quote | Live market quotes | | get_ohlc | Open, high, low, close data | | get_historical_data | Historical candle data (minute to daily) | | get_instruments | Search tradeable instruments across NSE, BSE, NFO, MCX | | place_order | Place buy/sell orders (market, limit, stop-loss) | | modify_order | Modify pending orders | | cancel_order | Cancel pending orders | | get_gtt_triggers | View Good Till Triggered orders | | place_gtt | Place GTT single or OCO (stoploss + target) triggers | **Key capabilities:** - Fully automated login -- TOTP generated on the fly, no manual intervention - Auto-retry on stale tokens -- re-authenticates transparently if a token expires mid-session - Supports delivery (CNC), intraday (MIS), and F&O (NRML) orders - After-market orders (AMO) supported Compatible with Works with any MCP-compatible client, including: | Client | Platform | |--------|----------| | Claude Desktop | macOS, Windows | | Claude Code | Terminal (macOS, Linux, Windows) | | Cursor | macOS, Windows, Linux | | Windsurf | macOS, Windows, Linux | | Continue | VS Code, JetBrains | | Any MCP-compatible client | See MCP clients list | Quick Start 1. Install 2. Get your credentials You need a Kite Connect API app. From your app dashboard, note your **API Key** and **API Secret**. You also need: - **User ID** -- your Zerodha client ID (e.g., AB1234) - **Password** -- your Zerodha login password - **TOTP Secret** (recommended) -- the base32 seed from setting up an external authenticator app for Zerodha 2FA. This enables fully automated login with no manual steps. How to get your TOTP secret 1. Log in to **console.zerodha.com** 2. Go to **My Profile** > **Security** > **2FA Settings** 3. Switch to an **external authenticator app** (Google Authenticator, Authy, etc.) 4. When the QR code appears, look for a **"Can't scan? Copy this key"** link 5. That key is your TOTP secret -- save it before completing setup 6. Enter the 6-digit code from your authenticator to finish 3. Configure your MCP client Add this to your MCP client configuration. The config location depends on your client -- refer to your client's documentation for the exact path.