How zerodha/kite-mcp-server works
Kite MCP Server exposes Kite Connect trading and account capabilities as MCP tools. The main workflow is an AI client connecting through a configured server mode, invoking a tool, and—when needed—logging in through a browser before the tool accesses Kite. The graph separates transport and registration, authentication/session management, account and trading tools, and market data. Source excerpts show key calls, but not every tool handler or HTTP route; unverified subsystem links are omitted.
Main entry points: manager.go Kite manager · mcp.go MCP tool registry · market_tools.go Market tools · app.go App and transports
Components 20
Server runtime
- Process entry
main.go - App and transports
app/app.go - MCP tool registry
mcp/mcp.go - Usage metrics
app/metrics/metrics.go
Authentication and sessions
- Kite manager
kc/manager.go - Session lifecycle
kc/session.go - Session signing
kc/session_signing.go - Auth templates
kc/templates - Login tool
mcp/setup_tools.go
Account and trading
- Tool helpers
mcp/common.go - Account queries
mcp/get_tools.go - Fund holdings
mcp/mf_tools.go - Orders and GTT
mcp/post_tools.go
Market data
- Market tools
mcp/market_tools.go - Instrument catalogue
kc/instruments/manager.go - Instrument search
kc/instruments/search.go - Instrument models
kc/instruments/instruments.go
Other components
- AI client
- User browser
- Kite Connect API
Connections 30
- AI client → App and transports: connects via MCP
README.md - Process entry → App and transports: starts
main.go - App and transports → Kite manager: creates
app/app.go - App and transports → MCP tool registry: registers tools
app/app.go - App and transports → Usage metrics: imports
app/app.go - MCP tool registry → Login tool: registers
mcp/mcp.go - Login tool → Kite manager: creates auth session
mcp/setup_tools.go - Login tool → User browser: presents login link
mcp/setup_tools.go - User browser → Kite manager: returns authorization
- Kite manager → Session lifecycle: manages sessions
kc/manager.go - Kite manager → Session signing: verifies session IDs
kc/manager.go - Kite manager → Auth templates: sets up templates
kc/manager.go - MCP tool registry → Account queries: registers
mcp/mcp.go - MCP tool registry → Fund holdings: registers
mcp/mcp.go - MCP tool registry → Orders and GTT: registers
mcp/mcp.go - MCP tool registry → Market tools: registers
mcp/mcp.go - Account queries → Tool helpers: uses helpers
mcp/get_tools.go - Orders and GTT → Tool helpers: uses helpers
mcp/post_tools.go - Market tools → Tool helpers: uses helpers
mcp/market_tools.go - Account queries → Kite manager: gets session
mcp/get_tools.go - Fund holdings → Kite manager: gets session
mcp/mf_tools.go - Orders and GTT → Kite manager: gets session
mcp/post_tools.go - Market tools → Kite manager: gets session
mcp/market_tools.go - Account queries → Kite Connect API: requests account data
mcp/get_tools.go - Fund holdings → Kite Connect API: requests fund holdings
mcp/mf_tools.go - Orders and GTT → Kite Connect API: submits trade requests
mcp/post_tools.go - Market tools → Kite Connect API: requests market data
mcp/market_tools.go - Market tools → Instrument catalogue: searches instruments
mcp/market_tools.go - Instrument catalogue → Instrument models: indexes instruments
kc/instruments/manager.go - Market tools → Instrument search: uses search
mcp/market_tools.go