For Zerodha Kite Connect API MCP Server

Open-source MCP server for Zerodha Kite Connect. Portfolio, market data, backtesting, alerts. Exposed over MCP by the for zerodha kite connect api mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

• ~9,000 tests — across 493 test files (44 in deploy repo + 449 in 32 externalized algo2go/kite-mcp-* modules) — run go test ./... -count=1 in each module
• AES-256-GCM encryption — at rest for every sensitive value — Kite tokens, API secrets, OAuth client secrets — key derived via HKDF from OAUTH_JWT_SECRET
• Per-tool-call audit trail — with 90-day retention — every MCP call logged to SQLite, CSV/JSON export via dashboard
• CI on every push — — go build, go vet, go test -race (see .github/workflows/ci.yml)
• MIT license, open source — — inspect anything. Upstream attribution to Zerodha Tech preserved in LICENSE
• Threat model — THREAT_MODEL.md. Security policy: SECURITY.md

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• AES-256 — GCM encryption** at rest for every sensitive value — Kite tokens, API secrets, OAuth client secrets — key derived via HKDF from OAUTH_JWT_SECRET
• Per-tool — call audit trail** with 90-day retention — every MCP call logged to SQLite, CSV/JSON export via dashboard
• Options — Black-Scholes Greeks (delta, gamma, theta, vega, IV), option chain, 8 multi-leg strategy templates
• Backtesting — 4 built-in strategies (SMA crossover, RSI reversal, breakout, mean reversion) with Sharpe ratio and max drawdown
• Alerts — price above/below, percentage drop/rise, composite conditions, volume spike, Telegram delivery + native Kite GTT alerts
• RiskGuard — 11 pre-trade checks run before every order hits the exchange (kill switch, order value cap, quantity limit, daily count, rate limit, per-second rate
• Development — bash
• CERT — In Directions (April 2022) — cybersecurity incident reporting
• Multi — user hosting** = empanelment required under §III(a) + broker-hosting mandate under NSE/INVG/67858 §I(h). Not supported by this repository.
• Algo — ID tagging** (mandatory from April 1, 2026): injected server-side by Zerodha OMS for <10 OPS retail users — no client-side action required
• Variable — Required
• OAUTH_JWT_SECRET — Yes (HTTP)

Configuration

You will need 8 environment variables: OAUTH_JWT_SECRET, KITE_API_KEY, KITE_API_SECRET, KITE_ACCESS_TOKEN, EXTERNAL_URL, ALERT_DB_PATH, TELEGRAM_BOT_TOKEN, GOOGLE_CLIENT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• A Kite Connect developer app (Rs 500/month from Zerodha) - npx (Node.js 18+) for mcp-remote — or Go 1.25+ to self-host from source

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch For Zerodha Kite Connect API.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the for zerodha kite connect api mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. For Zerodha Kite Connect API's toolset — AES-256, Per-tool, Options and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Sundeepg98; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.