-
Notifications
You must be signed in to change notification settings - Fork 2
FAQ
Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. Think of it as a USB port for AI β plug in any tool and the AI can use it.
Any MCP-compatible assistant:
- Claude Code (CLI)
- Claude Desktop
- Any app using the MCP SDK (Python, TypeScript, Ruby, Go)
- The server runs locally on your machine β no data goes through third-party servers
- Credentials are stored in your local
.envfile - Order placement always requires AI confirmation before execution
- The code is fully open-source β audit it yourself
The MCP server itself is free and open-source. However:
- Free tools (25): portfolio, orders, smart orders, instruments, profile β work with any Groww account
- Paid tools (5): quote, LTP, OHLC, option chain, historical data, backtesting β require Groww's Live Data subscription at βΉ499 + GST/month
TOTP β always. One-time 2-minute setup, then it works forever with zero daily maintenance.
- TOTP auth: Just restart the server. It auto-generates a fresh token.
- Approval auth: Visit Groww β Trading APIs β click "Approve", then restart.
- Manual token: Generate a new token on the Groww website.
Regenerate the TOTP token on the Groww website. The TOTP secret might have changed.
Yes, but the server picks the first available in priority order: TOTP > Approval > Manual.
They require the Groww Live Data subscription (βΉ499 + GST/month). Subscribe at: Groww App β Settings β Trading APIs.
Yes. place_order, modify_order, and cancel_order execute real trades with real money. The AI assistant will always confirm with you before placing an order.
- GTT (Good Till Triggered): Sets a price trigger β when the stock hits your target, an order is automatically placed
- OCO (One Cancels Other): Sets both stop-loss AND target β whichever hits first executes, the other cancels automatically
Other implementations don't cover the /v1/smart-order/* endpoints. We verified and implemented every available Groww API endpoint.
Ruby >= 3.1.0. Tested on Ruby 4.0.1.
Yes. Specify the full Ruby path in your .mcp.json config. See the Getting Started page for RVM-specific setup.
- The official MCP Ruby SDK is well-maintained (Anthropic + Shopify)
- Ruby's expressiveness makes tool definitions clean
- Strong HTTP/JSON support in stdlib
- Existing TypeScript and Python implementations had broken API paths
The server reads the token's expiry from the JWT payload and refreshes 5 minutes before expiry. For TOTP auth, it regenerates a fresh code and exchanges it for a new token. This happens silently β no user action needed.
Most use incorrect API endpoint paths (e.g., /portfolio/holdings instead of /v1/holdings/user). We verified every endpoint against the live Groww API and the official Groww Trade API documentation.
- Check Ruby version:
ruby --version(needs >= 3.1.0) - Run
bundle installto ensure gems are installed - Verify
.envhas valid credentials
Groww requires a registered static IP for order placement (SEBI compliance). Register yours at: Groww β Settings β Trading APIs β Add Static IP.
- Verify the path in
.mcp.jsonis correct - If using RVM, set
GEM_HOMEandGEM_PATHin the env config - Restart your AI assistant after changing
.mcp.json
Groww has strict rate limits (10 req/sec for orders, 20 req/sec for reads). The server auto-retries with backoff, but avoid rapid-fire queries.
Built by Jai Rajput | MIT License | Report an Issue
Setup
Reference
Community
Links