Kite Connect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KITE_API_KEY | Yes | Your Kite Connect API key | |
| KITE_ACCESS_TOKEN | Yes | Your Kite Connect access token |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buy_stockC | Buy a stock |
| sell_stockC | Sell a stock |
| greetA | Greet someone by name |
| add_two_numbersA | Calculate sum of two numbers. |
| factorialC | Calculate factorial of a number. |
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 5 tools
The stock tools (buy_stock, sell_stock) are distinct, and the math/greeting tools are also individually clear. However, the mix of unrelated domains within a single server creates confusion about tool selection and purpose.
buy_stock and sell_stock follow a consistent verb_noun pattern, but greet, add_two_numbers, and factorial use different styles (bare verb, verb_object, and noun). This inconsistency makes the API feel chaotic.
Five tools is a reasonable number, but for a stock trading server only two are relevant. The other three are unrelated, making the count misleading and the server's scope unfocused.
For a trading server, critical operations like get_quote, list_positions, or place_order variants are missing. Instead, the set includes non-trading utilities, creating severe gaps that prevent any real trading workflow.