Tools

Kite MCP exposes 7 grouped tools using a mode parameter and a help tool using a key path. Clients advertising the Skills extension use native Skills discovery in place of help. The AI assistant selects the appropriate tool and mode based on the user's request.

help

Browse bundled Markdown workflows with help({"key":"/"}), then follow child keys such as /orders/reconcile, /holdings/concentration, or /technical-analysis/moving-averages. Omitting key reads the root. Trailing slashes are accepted; keys are exact and case-sensitive. Unknown keys produce an MCP tool error with navigation instructions. This read-only tool requires no Kite API call and does not authorize transactions.

See Help and Skills for the catalog structure and Skills protocol interface.

Pagination contract

Paginated modes are portfolio holdings (full and compact), portfolio positions, orders list, orders all_trades, gtt list, market search, and market option_chain (strike rows).

• from is an integer from 0 to 2147483647, default 0.
• limit is an integer from 1 to 500, default 100. Zero, negative, fractional, string, and null values are rejected rather than coerced or treated as unlimited.
• These modes always return data and pagination, including when pagination arguments are omitted. An offset beyond the end returns an empty array and has_more: false. Continue with from + returned while has_more is true.
• Search results sort by id, then instrument_token, before slicing. Pages are stable for an unchanged instrument catalog; a catalog refresh can change matches.

{"data": [], "pagination": {"from": 0, "limit": 100, "total": 0, "returned": 0, "has_more": false}}

Response-shape change: clients previously reading bare arrays from these modes must now read data. Holdings summary, profile, margins, and other unpaginated operations retain their existing response shapes. Market quote/LTP/OHLC now use an explicit data/meta envelope as documented below.

portfolio

Retrieve portfolio and account information.

Parameters:

Position rows retain the upstream fields and add view: day for today's trading activity and net for current exposure including overnight holdings. Rows are paginated together, with day rows first. The same instrument may occur in both views; use net to assess current exposure and never sum the two views.

orders

Manage orders placed during the current trading day.

Placement, modification, and cancellation use form elicitation when the client advertises support (including legacy elicitation: {}). Clients that do not advertise form support, including URL-only clients, execute through the normal tool call without an additional server approval form. All order modes remain available in tools/list. Authentication and order validation still apply.

For capable clients, MCP 2026-07-28 uses per-request capabilities and InputRequiredResult with inputRequests, followed by a retry carrying inputResponses and opaque requestState. Older protocols use nested elicitation/create. The approval shows the normalized order parameters, including instrument, exchange, BUY/SELL, quantity, product, order type, price, and validity. Modification and cancellation also show the latest order history entry fetched from Kite; omitted modification fields remain unchanged. Placement defaults validity to DAY. The response must have action: "accept" and boolean content.confirm: true. An approved=true tool argument never grants approval.

When elicitation is used, declines, cancellations, missing or invalid confirmation, disconnects, and the two-minute deadline block execution. An elicitation failure never falls back to direct execution. Continuations still validate the original approval even if capabilities are omitted on the retry. Approval failures use the Trade approval failed [code] prefix, distinct from Kite API failures.

Multi-round-trip approval state expires after two minutes and is bound to the account session, operation, and normalized transaction details. It is consumed atomically before execution, so a retry cannot reuse an approval. Server restart invalidates pending approvals. Each account session can hold up to eight pending approvals, within a server-wide limit of 1,024. Expired or consumed approvals release capacity.

Each approval authorizes one API attempt with the parameters shown. The server does not automatically retry mutations; after an ambiguous API failure, inspect the order book before initiating another trade. On clients supporting form elicitation, a repeated tool call requires fresh approval. This is client-mediated consent through a trusted MCP client, not independent user authentication. GTT and Alerts/ATO are outside this approval gate.

Parameters:

gtt

Manage GTT (Good Till Triggered) orders. GTT orders persist across trading sessions and execute automatically when a price condition is met.

Parameters:

Single-leg parameters (when trigger_type=single):

Two-leg (OCO) parameters (when trigger_type=two-leg):

| from | integer | list | Pagination start index | | limit | integer | list | Page size: 1-500, default 100 |

open_kite_view

Model-visible on Apps-capable clients. Opens a read-only interactive Kite view with initial data. Required view: holdings, positions, funds, orders, gtt, option_chain, quote, historical, or search.

• option_chain: underlying (default NIFTY), optional exchange and expiry.
• quote: required instruments (up to 500 IDs).
• historical: required instrument_token, from_date, to_date, interval.
• search: required query, optional filter_on (default id).
• List views support from and limit with the normal pagination bounds.

The selector is filtered by server tool exclusions. It cannot place, modify, cancel, or delete orders/triggers. Use ordinary tools for text-only analysis or clients without Apps support.

market

Retrieve market data and search instruments.

Common parameters:

Quote, LTP, and OHLC return a consistent envelope:

{"data": {"NSE:INFY": {"last_price": 1500}}, "meta": {"requested_count": 2, "returned_count": 1, "missing_instruments": ["NSE:UNKNOWN"], "partial": true}}

data contains only resolved symbols from the request. Counts refer to unique symbols. meta.missing_instruments explicitly lists unresolved symbols; a partial response retains the successful data. If no symbols resolve, the response has isError: true, empty data, and an error message advising correction of the exchange/symbols. Missing symbols are not represented as zero-priced quotes.

Market successes expose identical values in JSON text content and structuredContent, with an advertised output schema covering data/meta envelopes and historical candles. Historical responses use {"data": [<candles>], "meta": {"timezone": "Asia/Kolkata"}}; clients previously reading a bare candle array must now read data. Object envelopes conform to the MCP 2025-11-25 output contract. LTP and OHLC metadata includes as_of_available: false and timestamp_note: these upstream endpoints supply no timestamps. Use mode=quote for upstream timestamp and last_trade_time; receipt time is not a price as-of timestamp.

Option-chain parameters (mode=option_chain):

data contains canonical underlying information, optional real spot and same-expiry future instrument records, the selected expiry, all available unexpired expiries, and sorted strikes. Each strike has strike, call, and put; missing sides are null. The index covers the entire loaded instrument catalog and includes active derivative contracts only. It is rebuilt atomically with catalog updates. loaded_at identifies that catalog snapshot.

Pagination counts strikes, not instruments. meta.complete and meta.truncated describe the returned page. Continue while has_more is true, using the selected data.expiry and catalog revision from page one. Chain formation makes no live quote calls; request mode=quote separately for contract IDs and distinguish the catalog's reference prices from current quotes.

{"mode":"option_chain","exchange":"NFO","underlying":"NIFTY","limit":500}

Historical parameters (mode=historical):

Search parameters (mode=search):

Search responses include a meta block. By default, instrument_data_source is bod_instruments, which means fields such as circuit limits come from the beginning-of-day instrument master. When include_live_quote=true, quotes are fetched only for the returned page. live_quote_enriched is true only if at least one result was enriched. The live_quote_fields list uses the actual output names: last_price, lower_circuit_limit, upper_circuit_limit, ohlc, and quote_timestamp. missing_live_quotes lists instruments for which enrichment was unavailable; those records retain their BOD values and have no invented quote timestamp. If no quotes resolve, live_quote_fields is empty. Enrichment describes the data source, not a guarantee of freshness: inspect the upstream quote_timestamp and market session when interpreting a returned price.

alerts

Manage Kite price alerts. Alerts trigger when a price condition is met.

Parameters:

mutual_funds

Retrieve mutual fund data from Coin.

Parameters:

session

Inspect or invalidate the current authenticated session.

Parameters: