Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Kite Connect MCP

by techfreakwormversion 0.1.1i★ –iRuns on your computer
Registry nameio.github.techfreakworm/kite-connect-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Online shops & payments
  • You need to fill in: KITE_API_KEY, KITE_API_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: KITE_API_KEY, KITE_API_SECRET, KITE_MCP_AUTH_MODE, KITE_TOKEN_FILE, KITE_MCP_TRADING_MODE, KITE_MCP_READ_ONLY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
      }
    }
  }
}

Run this in your terminal

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • KITE_API_KEY secret required env
    API key of your Kite Connect app (developers.kite.trade)
  • KITE_API_SECRET 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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account techfreakworm, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 1754 servers in this category
  • Published to the registry more recently than 86% of the other 1754 servers in this category
  • Basic checks equal to or better than 100% of the other 1754 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Kite Connect MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: KITE_API_KEY, KITE_API_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago
Install

MCP Cn Commerce

by TonyWang-hub

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

Runs on your computer★ 96MITUpdated 28 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

GuardDefault
Every write tool takes dry_runtrue: validate, run the checks, preview the exact request and Kite's margin calculation; send nothing
Live trading switchoff (KITE_MCP_TRADING_MODE=dry_run)
Confirmationa 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-listsinstruments, exchanges, products, varieties, order types, sides (all optional)
Read-only modeKITE_MCP_READ_ONLY=true hides every write tool, and the HTTP client refuses write endpoints too
Kill switcha file; a tool can switch it on, only a person can switch it off
Audit logevery dry run, refusal, live send and result, as JSON lines; the intent is fsynced *before* sending
Rate limitskept under Kite's 1/s (quotes), 3/s (historical), 10/s (orders and the rest), 400 orders/min
Retriesreads 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.

ToolsetTools
sessionsession_status, login, complete_login, logout
accountget_profile, get_margins
ordersplace_order, modify_order, cancel_order, get_orders, get_order_history, get_trades, get_order_trades
gttget_gtts, get_gtt, place_gtt_order, modify_gtt_order, delete_gtt_order
alertsget_alerts, get_alert, get_alert_history, create_alert (simple and ATO), modify_alert, delete_alerts
portfolioget_holdings, get_positions, get_auctions, convert_position, authorise_holdings
marketget_quotes, get_ohlc, get_ltp, get_historical_data, search_instruments, get_instrument, get_instruments_status, refresh_instruments
marginsget_order_margins, get_basket_margins, get_order_charges
mfget_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
tickerticker_subscribe, ticker_unsubscribe, ticker_get_ticks, ticker_status, ticker_order_updates, ticker_stop
safetyget_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.

Licence

MIT © 2026 Mayank Gupta

Ask PopNx