Zerodha MCP Integration
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KITE_API_KEY | Yes | Your Zerodha API Key (also called Consumer Key) | |
| KITE_API_SECRET | Yes | Your Zerodha API Secret (also called Consumer Secret) |
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 |
|---|---|
| initiate_loginA | Start the Zerodha login flow by opening the login URL in a browser and starting a local server to handle the redirect |
| get_request_tokenB | Get the current request token after login redirect |
| get_holdingsB | Get user's holdings/portfolio |
| get_positionsC | Get user's positions |
| get_marginsC | Get account margins |
| place_orderC | Place an order on Zerodha Args: tradingsymbol: Trading symbol (e.g., 'INFY') exchange: Exchange (NSE, BSE, NFO, etc.) transaction_type: BUY or SELL quantity: Number of shares/units product: Product code (CNC, MIS, NRML) order_type: Order type (MARKET, LIMIT, SL, SL-M) price: Price for LIMIT orders trigger_price: Trigger price for SL orders |
| get_quoteC | Get quote for symbols Args: symbols: List of symbols (e.g., ['NSE:INFY', 'BSE:RELIANCE']) |
| get_historical_dataC | Get historical data for an instrument Args: instrument_token: Instrument token from_date: From date (format: 2024-01-01) to_date: To date (format: 2024-03-13) interval: Candle interval (minute, day, 3minute, etc.) |
| check_and_authenticateB | Check if Kite is authenticated and initiate authentication if needed. Returns the authentication status and any relevant messages. |
| get_mf_ordersB | Get all mutual fund orders |
| place_mf_orderC | Place a mutual fund order Args: tradingsymbol: Trading symbol (e.g., 'INF090I01239') transaction_type: BUY or SELL amount: Amount to invest or redeem tag: Optional tag for the order |
| cancel_mf_orderC | Cancel a mutual fund order Args: order_id: Order ID to cancel |
| get_mf_instrumentsB | Get all available mutual fund instruments |
| get_mf_holdingsB | Get user's mutual fund holdings |
| get_mf_sipsB | Get all mutual fund SIPs |
| place_mf_sipB | Place a mutual fund SIP (Systematic Investment Plan) Args: tradingsymbol: Trading symbol (e.g., 'INF090I01239') amount: Amount per instalment instalments: Number of instalments (minimum 6) frequency: weekly, monthly, or quarterly initial_amount: Optional initial amount instalment_day: Optional day of month/week for instalment (1-31 for monthly, 1-7 for weekly) tag: Optional tag for the SIP |
| modify_mf_sipB | Modify a mutual fund SIP Args: sip_id: SIP ID to modify amount: New amount per instalment frequency: New frequency (weekly, monthly, or quarterly) instalments: New number of instalments instalment_day: New day of month/week for instalment status: SIP status (active or paused) |
| cancel_mf_sipC | Cancel a mutual fund SIP Args: sip_id: SIP ID to cancel |
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 18 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are well-organized into authentication, data retrieval, mutual fund operations, and trading operations, with clear boundaries between categories. For example, get_mf_holdings and get_holdings serve different asset classes, and place_mf_order versus place_order handle different instrument types.
Tool names follow a highly consistent verb_noun pattern throughout, with clear action prefixes (get_, place_, cancel_, modify_, initiate_, check_) followed by specific nouns. All tools use snake_case consistently, and naming conventions are predictable across the entire set, making it easy to understand tool purposes at a glance.
With 18 tools, this server provides comprehensive coverage for Zerodha trading and mutual fund operations without being overwhelming. The count is well-scoped for the domain, covering authentication, market data, portfolio management, mutual fund lifecycle, and order execution—each tool earns its place in supporting complete trading workflows.
The tool surface provides complete CRUD/lifecycle coverage for both trading and mutual fund domains. For mutual funds, it covers order placement, SIP management, holdings, instruments, and cancellation/modification. For trading, it covers order placement, positions, holdings, margins, and historical data. Authentication tools handle the complete login flow, leaving no obvious gaps for agent operations.