techfreakworm/kite-connect-mcp

A self-hostable Model Context Protocol server for the
Zerodha Kite Connect v3 API. Run it on your own machine or server with
your own Kite Connect app, and let an AI assistant read your account, market data and orders. Every write is a
dry run by default.
> Status: beta (0.x). Every Kite Connect v3 capability is covered and tested offline against a fake Kite;
> expect rough edges against the real API and report them. Changes are listed in CHANGELOG.md.
> This project is not affiliated with or endorsed by Zerodha.
## Why another Kite MCP server?
Zerodha publishes an official server (zerodha/kite-mcp-server) and
hosts it at mcp.kite.trade. This project differs in three ways:
It covers the whole paid Kite Connect API. That includes alerts, GTTs, order and basket margins, charges,
position conversion, holdings authorisation, auctions, mutual funds and the WebSocket ticker.
It's built for one person self-hosting. The daily token is persisted and shared by every client you connect.
It has a safety layer for orders: dry runs, two-step confirmation, value caps, allow-lists, a kill switch, an
audit log and rate limiting.
The full evaluation and reasoning are in docs/DECISION.md.
## What you need
A Zerodha account, and a Kite Connect app from the developer console.
Connect (paid, ₹500/month per API key) includes live quotes, the WebSocket and historical candles.
Personal (free) covers orders, GTTs, alerts, portfolio and margins, but no market data. Market-data tools
return a clear "needs the paid plan" error.
Python 3.11+ (or Docker).
To place live orders: the order requests must come from a static IP registered in the developer console.
This is a SEBI/NSE rule, in force since April 2026. Reads work from any IP.
The developer-console steps are in docs/KITESETUP.md: creating the app, the API key and
secret, the redirect and postback URLs, the subscription, and the static IP.
## Quick start (local, stdio)
bash
# install
uv tool install kite-connect-mcp # or: pipx install kite-connect-mcp / pip install kite-connect-mcp
# or run without installing: uvx kite-connect-mcp --help
# or the image: docker pull ghcr.io/techfreakworm/kite-connect-mcp
# configure: credentials from env vars or files (mode 600)
export KITEAPIKEY=yourapikey
export KITEAPISECRETFILE=~/.config/kite-connect-mcp/apisecret
kite-connect-mcp check-config # validates settings, never prints credentials
kite-connect-mcp login --listen # prints the Kite login link and waits for the redirect (managed mode)
kite-connect-mcp status # session and safety status
For login --listen, register http://127.0.0.1:8765/callback as your app's redirect URL. Every setting is listed in
docs/CONFIGURATION.md.
Add it to an MCP client, e.g. Claude Desktop (claudedesktopconfig.json) or any client that launches stdio servers:
json
"mcpServers": {
"kite": {
"command": "kite-connect-mcp",
"args": ["serve"],
"env": { "KITEAPIKEY": "yourapikey", "KITEAPISECRETFILE": "/home/you/.config/kite-connect-mcp/apisecret" }
To run it on a server over HTTP, see docs/SELFHOSTING.md. It covers systemd and Docker,
a reverse proxy with TLS, bearer-token auth, and the login callback.
## The safety model, in short