Kite Connect MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add kite-connect-mcp -e 'KITE_API_KEY=<KITE_API_KEY>' -- uvx kite-connect-mcp

{
  "mcpServers": {
    "kite-connect-mcp": {
      "command": "uvx",
      "args": [
        "kite-connect-mcp"
      ],
      "env": {
        "KITE_API_KEY": "<KITE_API_KEY>"
      }
    }
  }
}

[mcp_servers.kite-connect-mcp]
command = "uvx"
args = ["kite-connect-mcp"]
env = { KITE_API_KEY = "<KITE_API_KEY>" }

{
  "mcpServers": {
    "kite-connect-mcp": {
      "command": "uvx",
      "args": [
        "kite-connect-mcp"
      ],
      "env": {
        "KITE_API_KEY": "<KITE_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "kite-connect-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "kite-connect-mcp"
      ],
      "env": {
        "KITE_API_KEY": "<KITE_API_KEY>"
      }
    }
  }
}

Put your own value in place of <KITE_API_KEY> (API key of your Kite Connect app (developers.kite.trade)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: KITE_API_SECRET (API secret of your Kite Connect app, needed for the daily login (or use KITE_API_SECRET_FILE)), KITE_MCP_AUTH_MODE (managed (this server owns the daily login) or external (read a token file another program writes)), KITE_TOKEN_FILE (Path of the access-token file (default: ~/.local/state/kite-connect-mcp/access_token.json)), KITE_MCP_TRADING_MODE (dry_run (default: writes are only previewed) or live (writes need a confirmation token)), KITE_MCP_READ_ONLY (true hides every tool that can change the account).