[Integrations] Add Groww integration (Trade API + MCP)

Description

Add a Groww integration so CORE can read (and optionally act on) a user’s portfolio + trading activity, and log high-signal events into memory.

This is primarily a read-first integration (portfolio + orders + transactions + holdings). If Groww’s trading APIs allow it, we can extend later to actions (place/cancel orders).

Reference Implementations

• Groww product: https://groww.in/
• Groww Trade API docs (unofficial / community references):
  • https://github.com/zerodha/pykiteconnect (reference for patterns; not Groww)
  • https://github.com/ (TBD — add any reliable Groww API reference you find)
• Groww MCP (hosted): https://mcp.groww.in (if still active / publicly reachable)

Note: Groww does not have a widely-adopted, fully-public “official” developer platform like Zerodha Kite Connect. We should treat this integration as: (1) MCP-first if Groww’s MCP is usable, otherwise (2) browser/session-based data extraction with explicit user consent, or (3) defer until an official API is confirmed.

Required Files Structure

packages/core/src/integrations/groww/
  index.ts
  client.ts
  types.ts
  mappers.ts
  auth.ts
  README.md
packages/core/src/integrations/groww/__tests__/
  groww.test.ts

Groww Integration

Auth

• Confirm supported auth mechanism:
  • If MCP: whatever auth the MCP server expects (token / session / OAuth).
  • If HTTP API exists: likely cookie/session-based or private mobile endpoints (avoid unless sanctioned).
• Store secrets in CORE’s standard integration secret store.
• Ensure refresh / expiry handling is explicit (fail gracefully; prompt re-auth).

Core Objects To Fetch

• Profile / account summary
• Holdings
• Positions
• Orders (open + historical)
• Transactions / contract notes

Events to Track

Track high-signal events that matter for memory + workflows:

• New order placed
• Order filled
• Order cancelled
• Large buy/sell (over a configurable threshold)
• New holding added (new symbol)
• Dividend / corporate action credit (if available)

Implementation Tasks

• Confirm whether Groww offers a usable official API and/or MCP server (document findings here)
• Implement auth
• Implement API/MCP client
• Map Groww objects → CORE canonical schema
• Add polling / sync job
• Emit events into memory store
• Add docs + README
• Add tests

Technical Notes

• Prefer MCP-first if Groww’s MCP endpoint is stable and supports required resources/tools.
• If no official API, avoid brittle scraping unless explicitly approved; document tradeoffs.

Resources

• GitHub issue #180 (PostHog integration pattern): https://github.com/RedPlanetHQ/core/issues/180

Labels

• integrations
• good first issue
• coding