About Kite MCP Server
Kite MCP Server connects Claude to the Zerodha Kite API for account holders who need portfolio, market data, and order operations. It uses OAuth 2.0 authentication and persists access tokens locally.
Key features
- 01View positions, holdings, and orders
- 02Retrieve live quotes and instruments
- 03Place, modify, and cancel orders
- 04View profile and margin details
- 05OAuth 2.0 authentication and token persistence
Use cases
- 01Review current positions and long-term holdings
- 02Look up instrument prices and quotes
- 03Submit or cancel trading orders
MCP support
The MCP server exposes Kite account, market data, and order-management tools to Claude.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEKite MCP Server
A Model Context Protocol (MCP) server for integrating with Zerodha Kite API. This server provides Claude with tools to interact with your Kite trading account.
Features
- Portfolio Management: Get positions, holdings, and orders
- Market Data: Real-time quotes, LTP, and instrument data
- Order Management: Place, modify, and cancel orders
- Account Info: Profile, margins, and authentication status
- Secure Authentication: OAuth 2.0 flow with token persistence
Prerequisites
- Zerodha Kite Connect App: Create an app at Kite Connect
- API Credentials: Get your API Key and Secret
- Bun: Latest version of Bun runtime
Installation
- Clone and install dependencies:
bun install
- Set up environment variables:
# Edit .env with your API credentials
- Configure your Kite Connect app with redirect URL:
http://localhost:50000/zerodha/auth/redirect
Quick Start
1. Authenticate with Kite API
bun run auth
This will:
- Start a local OAuth server
- Open your browser to Kite login
- Save your access token securely
2. Start the MCP Server
bun start
3. Configure Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"kite": {
"command": "bun",
"args": ["run", "/path/to/kite-mcp/src/index.ts"]
}
}
}
Available Tools
Portfolio Tools
get_profile- Get user profile informationget_positions- Get current trading positionsget_holdings- Get long-term holdingsget_margins- Get account margins and funds
Order Tools
get_orders- Get today's ordersplace_order- Place a new trading ordercancel_order- Cancel an existing order
Market Data Tools
get_ltp- Get Last Traded Price for instrumentsget_quote- Get detailed market quotesget_instruments- Get tradable instruments list
Utility Tools
get_auth_status- Check authentication status
Project Structure
src/
├── config/
│ └── environment.ts # Configuration management
├── auth/
│ ├── token-manager.ts # Token storage and validation
│ └── oauth-server.ts # OAuth flow handling
├── api/
│ └── kite-client.ts # Kite API wrapper
├── mcp/
│ ├── server.ts # MCP server implementation
│ └── tools/
│ └── index.ts # MCP tools definitions
├── auth.ts # Authentication entry point
└── index.ts # MCP server entry point
Development
Build (Optional)
bun run build
Development Mode
bun run dev # Watch mode for MCP server
bun run dev:auth # Watch mode for auth server
Architecture
The project follows the Single Responsibility Principle:
- ConfigManager: Environment and configuration handling
- TokenManager: Token persistence and validation
- OAuthServer: OAuth 2.0 authentication flow
- KiteClient: Kite API wrapper with error handling
- KiteMCPServer: MCP protocol implementation
- Tools: Individual MCP tool implementations
Environment Variables
API_KEY=your_kite_api_key # Required: Kite Connect API Key
API_SECRET=your_kite_api_secret # Required: Kite Connect API Secret
OAUTH_PORT=50000 # Optional: OAuth server port (default: 50000)
Security
- Tokens are stored locally in
access_token.json - OAuth flow uses secure redirect handling
- API credentials are never logged or exposed
- Tokens auto-expire for security
Troubleshooting
Authentication Issues
- Verify API credentials in
.env - Check redirect URL in Kite Connect app settings
- Ensure OAuth port (50000) is available
Token Expiry
- Kite tokens expire every ~6 hours
- Re-run
bun run authwhen expired - Server will notify you of authentication status
MCP Connection Issues
- Verify Claude Desktop configuration
- Check server is running:
bun start - Look for errors in Claude Desktop logs
Contributing
- Fork the repository
- Create a feature branch
- Follow the existing code structure and patterns
- Add appropriate error handling
- Submit a pull request
License
MIT License - see LICENSE file for details
Disclaimer
This is an unofficial integration with Zerodha Kite API. Use at your own risk. Always verify trades and orders before execution.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.