What a bank-client relationship looks like when banks control the data behind the UX

The relationship between clients and banks has been structured around a destination model, where businesses log in, navigate dashboards, export data, and piece together insights.

Grasshopper is working to dismantle that model.

In August 2025, the digital bank launched its Model Context Protocol (MCP) server in partnership with enterprise-grade digital banking solutions provider Narmi to address a specific challenge: enabling clients to use modern AI tools with their financial data without compromising banking security and control standards.

Nate Gruendemann, Director of Product at Grasshopper

“We learned people were uploading their bank statements or transaction files to their [external] AI of choice to run AI-analysis on their finances,” says Nate Gruendemann, Director of Product at Grasshopper. “MCP technology is how we close that gap.”

Technically, MCP sits between Grasshopper’s core banking systems and external AI models, managing authentication, permissions, and data structuring before any client-specific bank data reaches the AI model (e.g., Claude or ChatGPT). 

“In practice, this allows us to expose meaningful financial context while keeping the core banking system insulated,” notes Gruendemann.

But the key design choice lies in what MCP doesn’t allow. The system is built on the assumption that AI models are untrusted environments. MCP is fully opt-in, which means clients must authorize Claude or ChatGPT and authenticate with their banking credentials. The server can see only the data the user is permitted to access, and the entire system is currently read-only. This means AI tools and platforms can analyze information, but cannot act on it independently. For example, they cannot initiate transactions or modify account data.

“We secure the banking infrastructure and access layer, while clients maintain control over how they use their chosen AI tools,” adds Gruendemann.

This indicates Grasshopper isn’t focused on owning the user experience, but on controlling the underlying data layer that powers it.

The rationale behind building a user-facing layer outside the core banking system

  …


Tearsheet Pro