Kite Connect MCP

Name: Kite Connect MCP
Author: techfreakworm

作者：techfreakworm版本 0.1.1i★ –i在你的电脑上运行

注册名称io.github.techfreakworm/kite-connect-mcp

安装

概览

作者提供的说明（英文原文）

Zerodha Kite Connect v3 for AI agents: orders (dry-run by default), GTT, alerts, portfolio, quotes

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 网店与支付
你需要填写：KITE_API_KEY, KITE_API_SECRET

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： KITE_API_KEY, KITE_API_SECRET, KITE_MCP_AUTH_MODE, KITE_TOKEN_FILE, KITE_MCP_TRADING_MODE, KITE_MCP_READ_ONLY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "kite-connect": {
      "command": "uvx",
      "args": [
        "kite-connect-mcp",
        "serve"
      ],
      "env": {
        "KITE_API_KEY": "your-value",
        "KITE_API_SECRET": "your-value",
        "KITE_MCP_AUTH_MODE": "your-value",
        "KITE_TOKEN_FILE": "your-value",
        "KITE_MCP_TRADING_MODE": "your-value",
        "KITE_MCP_READ_ONLY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add kite-connect --env KITE_API_KEY=your-value --env KITE_API_SECRET=your-value --env KITE_MCP_AUTH_MODE=your-value --env KITE_TOKEN_FILE=your-value --env KITE_MCP_TRADING_MODE=your-value --env KITE_MCP_READ_ONLY=your-value -- uvx kite-connect-mcp serve

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "kite-connect": {
      "command": "uvx",
      "args": [
        "kite-connect-mcp",
        "serve"
      ],
      "env": {
        "KITE_API_KEY": "your-value",
        "KITE_API_SECRET": "your-value",
        "KITE_MCP_AUTH_MODE": "your-value",
        "KITE_TOKEN_FILE": "your-value",
        "KITE_MCP_TRADING_MODE": "your-value",
        "KITE_MCP_READ_ONLY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "kite-connect": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "kite-connect-mcp",
        "serve"
      ],
      "env": {
        "KITE_API_KEY": "your-value",
        "KITE_API_SECRET": "your-value",
        "KITE_MCP_AUTH_MODE": "your-value",
        "KITE_TOKEN_FILE": "your-value",
        "KITE_MCP_TRADING_MODE": "your-value",
        "KITE_MCP_READ_ONLY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

KITE_API_KEY 机密必填 env
API key of your Kite Connect app (developers.kite.trade)
KITE_API_SECRET 机密 env
API secret of your Kite Connect app, needed for the daily login (or use KITE_API_SECRET_FILE)
KITE_MCP_AUTH_MODE env
managed (this server owns the daily login) or external (read a token file another program writes)
KITE_TOKEN_FILE env
Path of the access-token file (default: ~/.local/state/kite-connect-mcp/access_token.json)
KITE_MCP_TRADING_MODE env
dry_run (default: writes are only previewed) or live (writes need a confirmation token)
KITE_MCP_READ_ONLY env
true hides every tool that can change the account

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 techfreakworm 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网店与支付”中的其他服务器比较i

星标数多于此分类中其他 1753 个服务器的 0%
发布到注册中心的时间比此分类中其他 1753 个服务器的 86% 更新
基础检查结果等于或优于此分类中其他 1753 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Kite Connect MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：KITE_API_KEY, KITE_API_SECRET

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.1）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spree Commerce: open-source B2B and marketplace ecommerce

作者：spree

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

在云端运行★ 15,812BSD-3-Clause8天前更新

安装

Stripe MCP

作者：stripe

MCP server integrating with Stripe - tools for customers, products, payments, and more.

在云端运行★ 2,043MIT12个月前更新

安装

MCP Cn Commerce

作者：TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

在你的电脑上运行★ 96MIT28天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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. The

read tools, the margin and charge calculators and the ticker have also been checked against the live API; live

writes (orders, GTTs, alerts, mutual funds) have not, so expect rough edges there 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/KITE_SETUP.md: creating the app, the API key and secret, the redirect and postback URLs, the subscription, and the static IP.

Quick start (local, stdio)

# 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 KITE_API_KEY=your_api_key export KITE_API_SECRET_FILE=~/.config/kite-connect-mcp/api_secret

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 (claude_desktop_config.json) or any client that launches stdio servers:

"mcpServers": { "kite": { "command": "kite-connect-mcp", "args": ["serve"], "env": { "KITE_API_KEY": "your_api_key", "KITE_API_SECRET_FILE": "/home/you/.config/kite-connect-mcp/api_secret" } } } }

To run it on a server over HTTP, see docs/SELF_HOSTING.md. It covers systemd and Docker, a reverse proxy with TLS, bearer-token auth, and the login callback.

The safety model, in short

Guard	Default
Every write tool takes `dry_run`	`true`: validate, run the checks, preview the exact request and Kite's margin calculation; send nothing
Live trading switch	off (`KITE_MCP_TRADING_MODE=dry_run`)
Confirmation	a live write needs the single-use `confirmation_token` from a dry run of the identical call (or, if you opt in, an explicitly allow-listed instrument)
Value caps	₹10,000 per order, ₹50,000 per day, 20 live orders per day
Allow-lists	instruments, exchanges, products, varieties, order types, sides (all optional)
Read-only mode	`KITE_MCP_READ_ONLY=true` hides every write tool, and the HTTP client refuses write endpoints too
Kill switch	a file; a tool can switch it on, only a person can switch it off
Audit log	every dry run, refusal, live send and result, as JSON lines; the intent is fsynced before sending
Rate limits	kept under Kite's 1/s (quotes), 3/s (historical), 10/s (orders and the rest), 400 orders/min
Retries	reads back off and retry; writes are never retried. A timeout is reported as an unknown outcome: check the order book before trying again

Details: docs/SAFETY.md.

Sessions and the daily login

Kite access tokens expire every day at about 06:00 IST. A request token is single-use. Logging in again with the same API key invalidates the previous access token. So one app should have exactly one program that owns the daily login.

`managed` mode (default). This server owns the login. The login tool (or kite-connect-mcp login) gives you the link. Kite redirects to this server's /callback, which checks the one-time state, exchanges the request_token, and stores the token with mode 600.
`external` mode. Another program owns the login and writes a token file. This server only reads that file, picks up the new token every morning without a restart, and never writes, deletes or logs out that token.

Tools

58 tools in 11 toolsets (53 by default: the mutual-fund writes are opt-in). Tool names follow the official server where one exists, so prompts carry over. Pick toolsets with KITE_MCP_TOOLSETS and hide single tools with KITE_MCP_EXCLUDED_TOOLS; kite-connect-mcp tools lists what your configuration exposes.

Toolset	Tools
session	`session_status`, `login`, `complete_login`, `logout`
account	`get_profile`, `get_margins`
orders	`place_order`, `modify_order`, `cancel_order`, `get_orders`, `get_order_history`, `get_trades`, `get_order_trades`
gtt	`get_gtts`, `get_gtt`, `place_gtt_order`, `modify_gtt_order`, `delete_gtt_order`
alerts	`get_alerts`, `get_alert`, `get_alert_history`, `create_alert` (simple and ATO), `modify_alert`, `delete_alerts`
portfolio	`get_holdings`, `get_positions`, `get_auctions`, `convert_position`, `authorise_holdings`
market	`get_quotes`, `get_ohlc`, `get_ltp`, `get_historical_data`, `search_instruments`, `get_instrument`, `get_instruments_status`, `refresh_instruments`
margins	`get_order_margins`, `get_basket_margins`, `get_order_charges`
mf	`get_mf_holdings`, `get_mf_orders`, `get_mf_sips`, `search_mf_instruments`; opt-in: `place_mf_order`, `cancel_mf_order`, `place_mf_sip`, `modify_mf_sip`, `cancel_mf_sip`
ticker	`ticker_subscribe`, `ticker_unsubscribe`, `ticker_get_ticks`, `ticker_status`, `ticker_order_updates`, `ticker_stop`
safety	`get_safety_status`, `get_audit_log`, `engage_kill_switch`

Every argument of every tool is in docs/TOOLS.md.

Development

git clone https://github.com/techfreakworm/kite-connect-mcp && cd kite-connect-mcp

python -m venv .venv && .venv/bin/pip install -e ".[dev]" .venv/bin/pytest # never touches the network: Kite is faked in-process .venv/bin/ruff check . && .venv/bin/ruff format --check .

See CONTRIBUTING.md. Security reports: SECURITY.md.

Disclaimer

Trading involves risk. This software can place real orders on a real brokerage account when you configure it to. AI systems are unpredictable: keep the caps low, use dry runs, and review what you confirm. The software is provided "as is", without warranty of any kind (see LICENSE). You are responsible for complying with Zerodha's terms, SEBI's rules (including the static-IP and algo rules) and exchange data policies. Kite Connect data may not be redistributed.