Kite MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List all available Kite accounts configured in the system. Returns account IDs and display names. Use this to show available accounts to the user. |
| loginA | Login to Kite API for a specific account. This tool helps you log in to the Kite API. If you are starting off a new conversation call this tool before hand. Call this if you get a session error. Returns a link that the user should click to authorize access, present as markdown if your client supports so that they can click it easily when rendered. |
| generate_sessionB | Generate session using request token. After user authorizes, call this with the request_token from the redirect URL to complete authentication. |
| get_profileB | Retrieve the user's profile information, including user ID, name, email, and account details like products orders, and exchanges available to the user. Use this to get basic user details. |
| get_marginsD | Get margins |
| place_orderC | Place an order |
| modify_orderC | Modify an existing order |
| cancel_orderC | Cancel an existing order |
| get_ordersC | Get all orders. Supports pagination for large datasets. |
| get_order_historyC | Get order history for a specific order |
| get_order_tradesC | Get trades for a specific order |
| get_tradesB | Get trading history. Supports pagination for large datasets. |
| get_positionsC | Get current positions. Supports pagination for large datasets. |
| get_holdingsA | Get holdings for the current user. Supports pagination for large datasets. |
| get_mf_holdingsB | Get all mutual fund holdings. Supports pagination for large datasets. |
| search_instrumentsC | Search instruments. Supports pagination for large result sets. |
| get_quotesB | Get market data quotes for a list of instruments |
| get_ohlcC | Get OHLC (Open, High, Low, Close) data for a list of instruments |
| get_ltpC | Get latest trading prices for a list of instruments |
| get_historical_dataC | Get historical price data for an instrument |
| place_gtt_orderC | Place a GTT (Good Till Triggered) order |
| modify_gtt_orderC | Modify an existing GTT (Good Till Triggered) order |
| delete_gtt_orderC | Delete an existing GTT (Good Till Triggered) order |
| get_gttsA | Get all active GTT orders. Supports pagination for large datasets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Most tools have distinct purposes, but there is some overlap between get_orders, get_order_history, and get_order_trades, which could cause confusion in selecting the right one for order-related queries. Additionally, get_ltp and get_quotes both provide price data, though they differ in scope (latest trading prices vs. market data quotes).
Tool names follow a consistent verb_noun pattern throughout, such as cancel_order, get_holdings, and place_gtt_order. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 24 tools, the count is borderline high for a trading API server, potentially overwhelming for agents. While it covers many functionalities, it might benefit from consolidation or better scoping to reduce complexity.
The tool set provides comprehensive coverage for a trading domain, including authentication (generate_session, login), account management (list_accounts, get_profile), order handling (place, modify, cancel), market data (get_historical_data, get_quotes), and holdings/positions. No obvious gaps are present for core trading workflows.