kite_place_orderLABSCO SUMMARY
Order entry, not just a read-only view of the portfolio.
Reading positions is the easy half — this one also places and cancels live orders, so the credential you connect can move real money. Everything a Kite session sees comes with it: the order book, day and net positions, the delivery portfolio, margins, live quotes and historical candles.
What it is
A server over Zerodha's Kite Connect API for Indian equity and derivatives trading. It places and cancels orders and reads back the order book, day and net positions, delivery holdings, margins, live quotes and historical candles. It is hosted rather than installed — credentials sit with the host and each tool is called over HTTP.
What you get
- Orders on NSE, BSE, NFO and MCX — market, limit and both stop-loss forms, with intraday, delivery and overnight product codes
- The order book with status, filled quantity and average price on every order
- Cancellation of a pending order by its ID, across every order variety Kite supports
- Day and net positions with profit and loss, and the delivery portfolio with average price against last price
- Live quotes for several instruments in one call, including volume and the day's circuit limits
- OHLCV candles over a date range, at intervals from a minute up to a full day
- The tradable instrument list, filterable by exchange — this is where instrument tokens come from
- Account margins for the equity and commodity segments, and the logged-in user's profile
- A readiness check that answers without credentials
Requirements
A Zerodha account plus an app created in the Kite Connect developer console, which yields an API key and secret. The access token you actually trade with comes from a login flow and is valid for one trading day only, so anything left running needs a fresh login each morning. The api_key and that day's access_token go into the MewCP dashboard under Credentials, not into your client's configuration. Calls are metered against the host account's request credits.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Checking where the portfolio stands before the open
Read delivery holdings and net positions together, both with profit and loss, then look at what margin is actually free.
02
Placing an order and confirming it landed
Send the order, then read the order book back for its status and the average price it filled at.
03
Pulling out of a trade that never filled
Find the pending order in the order book and cancel it by its ID.
04
Testing an idea against real candles
Look up the instrument token for the symbol, then pull OHLCV candles for it over the range and interval you want.
05
Watching a handful of symbols live
Ask for quotes on several instruments at once and read last price, volume and circuit limits out of one response.
06
Separating a connection problem from a credential problem
The readiness check answers without credentials, so if it responds and a trading call does not, the fault is the login rather than the link.
11 tools
Listed in project docs. Your client may show a different list.
kite_get_orderskite_cancel_orderkite_get_positionskite_get_holdingskite_get_quotekite_get_historical_datakite_get_instrumentskite_get_profilekite_get_marginskite_health_checkBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- A MewCP account — the Hobby tier is free (unlimited servers, 20K actions/month)
- The Kite server enabled in your MewCP toolset — the gateway only reaches servers you have enabled
- Your Kite Connect api_key and access_token, added as a static credential under Credentials in the MewCP dashboard — the access token is valid for one trading day, so it is replaced each morning
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
ENDPOINT URL
https://gateway.mewcp.com/personal/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"mewcp": {
"type": "http",
"url": "https://gateway.mewcp.com/personal/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MEWCP_KEY>"
}
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"mewcp": {
"url": "https://gateway.mewcp.com/personal/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MEWCP_KEY>"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mewcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://gateway.mewcp.com/personal/mcp",
"--transport",
"http-only",
"--header",
"Authorization: Bearer <YOUR_MEWCP_KEY>"
]
}
}
}
