Open-source MCP server for Zerodha Kite Connect. Portfolio, market data, backtesting, alerts.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Give Claude or ChatGPT direct access to your Zerodha Kite trading account β with order placement, paper trading, options Greeks, backtesting, Telegram alerts, and 11 pre-trade safety checks. 110+ tools. Open source, MIT.
Try the hosted demo (read-only) Β· Self-host in 60 seconds (full trading) Β· Compare vs official Zerodha MCP
Then say: "Log me in to Kite. Show my portfolio. Backtest SMA crossover on INFY. Set an alert for RELIANCE 2% drop."
Works inside Claude Desktop, Claude Code, claude.ai, ChatGPT Connectors, Cursor, VS Code Copilot, Windsurf β anything MCP-compliant. Complementary to Zerodha's official read-only MCP (22 tools, GTT only); this server adds order placement, alerts, paper trading, options Greeks, and analytics.
algo2go/kite-mcp-* modules) β run go test ./... -count=1 in each moduleOAUTH_JWT_SECRETalgo2go/kite-mcp-riskguard/guard.go (16 RejectionReason constants total; 11 fire on every trade).go build, go vet, go test -race (see .github/workflows/ci.yml)Point your MCP client at:
Order-placement tools are gated off on the hosted instance pursuant to NSE/INVG/69255 Annexure I Para 2.8. Read-only tools (portfolio, market data, backtesting, analytics) work. You still bring your own Kite developer app (per-user OAuth).
Point your client at http://localhost:8080/mcp (use --allow-http if your client requires it). Running locally against your own Kite account is the personal-use safe-harbor path β you remain the Zerodha Client; the software just helps you place orders.
Go users can skip Docker: go build -o kite-mcp-server && ./kite-mcp-server.
Add this to your client config (~/.claude.json, claude_desktop_config.json, .vscode/mcp.json, etc.):
Then say: "Log me in to Kite" β complete the OAuth flow in your browser β then ask anything: "Show my portfolio", "Backtest SMA crossover on INFY", "Enable paper trading mode".
New to this? Start with paper trading: "Enable paper trading mode" β virtual Rs 1 crore portfolio, no real money at risk.
Windows + Claude Code footnote: On Windows,
cmd /csilently swallows JSON args containing escaped quotes (\"). If you need to pass static OAuth client info tomcp-remote, write the JSON to a file and reference it via--static-oauth-client-info @path/to/client-info.jsoninstead of inline. Example client-info file lives at~/.claude/mcp-servers/kite-fly-client.jsonin the canonical Windows setup.
OAuth discovery follows the standards: RFC 8414 (OAuth 2.0 Authorization Server Metadata at /.well-known/oauth-authorization-server) and RFC 9728 (OAuth 2.0 Protected Resource Metadata at /.well-known/oauth-protected-resource). mcp-remote auto-discovers via these endpoints β no manual auth configuration required on the client side.
/buy, /sell, /quick, /setalert with inline keyboard confirmation; morning briefing (9 AM IST) and daily P&L (3:35 PM IST)Full tool taxonomy with counts per category in ARCHITECTURE.md.
Clean / hexagonal architecture:
Go 1.25 + mcp-go v0.46.0. SQLite for persistence (credentials, alerts, sessions, audit trail β all AES-256-GCM encrypted), with Litestream continuous replication to Cloudflare R2. OAuth 2.1 + PKCE, each user brings their own Kite developer app. Middleware chain: Timeout -> Audit -> Hooks -> RiskGuard -> Rate Limiter -> Billing -> Paper Trading -> Dashboard URL. Deployed on Fly.io (Mumbai region) with static egress IP for SEBI-mandated whitelisting. See ARCHITECTURE.md.
Not a SEBI-registered intermediary. This is infrastructure software, not an advisory or brokerage service.
- Per-user BYO Kite developer app β you remain the Zerodha Client of record. The server holds no pooled user funds and executes no trades on its own behalf.
- The hosted deployment at
kite-mcp-server.fly.devis read-only; order-placement tools are gated off pursuant to NSE/INVG/69255 Annexure I Para 2.8. Order placement requires running the server locally against your own account.- Running the server locally against your personal Kite account is the personal-use safe-harbor path β analogous to running your own algo script. See OpenAlgo's framing of the compliance landscape for Indian algo vendors.
- Static egress IP (
209.71.68.157, Mumbai) is published so users can whitelist it in their Kite developer console per the SEBI April 2026 mandate.- TERMS.md and PRIVACY.md are DRAFT and under independent legal review. Do not rely on them as final legal agreements.
- Trading involves risk. This software is not financial advice. Not affiliated with Zerodha.
OAUTH_JWT_SECRET is the only required variable for multi-user HTTP deployments. Everything else is optional and activates specific features when set. Full table:
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/mcp-server-for-zerodha-kite-connect-api)<a href="https://allmcps.com/mcp/mcp-server-for-zerodha-kite-connect-api"><img src="https://allmcps.com/api/badge/mcp-server-for-zerodha-kite-connect-api?style=directory" alt="MCP Server for Zerodha Kite Connect API on AllMCPs" /></a>