Angel One SmartAPI MCP for orders, portfolio, market data, GTT rules, charges, and margin.
TypeScript Model Context Protocol server for Angel One SmartAPI.
Use it from Claude, Cursor, Copilot, or any MCP client to:
fetch() integration. No Angel One SDK dependency.npx.angel-one-mcpio.github.ameernoufil/angel-oneameernoufil/angel-one-mcpIf your client supports registry-based discovery, search for io.github.ameernoufil/angel-one.
If your client prefers package installs, use angel-one-mcp from npm.
npx (recommended)Add this to your MCP client config:
{
"mcpServers": {
"angel-one": {
"type": "stdio",
"command": "npx",
"args": ["-y", "angel-one-mcp"],
"env": {
"ANGEL_API_KEY": "your_smartapi_key",
"ANGEL_CLIENT_ID": "your_client_id",
"ANGEL_PASSWORD": "your_mpin",
"ANGEL_TOTP_SECRET": "your_base32_totp_secret"
}
}
}
}
git clone https://github.com/ameernoufil/angel-one-mcp.git
cd angel-one-mcp
npm install
cp .env.example .env
npm run build
npm start
If running from source, point your MCP client to build/index.js.
Required:
ANGEL_API_KEYANGEL_CLIENT_IDANGEL_PASSWORDANGEL_TOTP_SECRETOptional safety limits:
SOFT_MAX_ORDER_QTY default 25HARD_MAX_ORDER_QTY default 100SOFT_MAX_ORDER_VALUE default 10000HARD_MAX_ORDER_VALUE default 100000Example .env:
ANGEL_API_KEY=your_smartapi_key
ANGEL_CLIENT_ID=your_client_id
ANGEL_PASSWORD=your_mpin
ANGEL_TOTP_SECRET=your_base32_totp_secret
Trading mutations are guarded.
Soft limits block by default and can be overridden with force: true.
Hard limits cannot be bypassed without changing env vars and restarting the server.
Guarded operations include:
place_ordermodify_ordercreate_gtt_rulemodify_gtt_ruleconvert_positionFor MARKET orders, the server attempts LTP-based value checks before allowing the request.
For an agent-focused onboarding prompt, see docs/llm-setup.md.
Requirements:
Commands:
npm install
npm run build
npm run lint
npm run lint:fix
npm run format
npm run dev
npm start
src/index.tssrc/api.tssrc/config.tssrc/guards.tssrc/tools/index.tssrc/tools/*.tsSource-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y angel-one-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ameernoufil-angel-one": {
"command": "npx",
"args": [
"-y",
"angel-one-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceangel-one-mcpnpmAngel One works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.