Building an MCP Server on ICICI Bank's Real API Banking Portal

There is no official, ICICI Bank-branded MCP server as of this writing. What ICICI Bank does have — and it's substantial — is its own API Banking portal, which the bank itself describes as India's largest, launched with nearly 250 documented APIs spanning payments, collections, trade finance, and account services. That's real, existing infrastructure, and it's exactly the kind of thing this site's guides elsewhere show being wrapped in a thin MCP layer rather than waiting for a vendor to ship one.

What Actually Exists Today

Separately from the corporate API Banking portal, there is a real, community-built MCP server for ICICI Direct — ICICI's brokerage arm — that wraps the Breeze API to let AI assistants query market data and manage trading sessions. That's a different product from corporate/retail banking APIs, and it's community-maintained, not an ICICI Bank official release. If your interest is trading rather than banking operations, similar community-built broker MCP servers exist for Upstox and Groww, following the same unofficial, third-party pattern.

What You'd Actually Build

To wrap ICICI's API Banking portal in an MCP server, the real steps look like:

1. Register for a developer account on ICICI Bank's API Banking portal and complete their onboarding/KYC process for API access.
2. Obtain sandbox credentials and test against ICICI's documented endpoints before requesting production access.
3. Pick a narrow, well-defined slice of the ~250 available APIs — account statement retrieval or payment initiation status, for example — rather than trying to wrap the entire surface at once.
4. Expose that slice as MCP tools with explicit, scoped permissions, following the same pattern this site documents for wrapping any existing production API in an MCP server.
5. Keep write operations (payment initiation, fund transfers) behind an explicit confirmation step — the same rule that applies to every payment- or banking-capable MCP server covered on this site.

Why No Official One Exists Yet

Banking APIs carry regulatory and security obligations well beyond a typical SaaS integration — KYC, RBI compliance, audit trails, and liability for erroneous transactions all apply. That's almost certainly why India's major banks have invested in API Banking portals (real, documented, developer-facing infrastructure) rather than rushing to publish an AI-facing MCP layer on top of it the way consumer platforms like Zomato or Swiggy have. If ICICI or another major bank does ship an official MCP server, it will very likely sit behind the same kind of onboarding, sandboxing, and compliance review their existing API Banking portal already requires.