Today for "Agent Dispatch#1":
--
When people talk about the future of software, they often focus on what the model can do. But the real shift may be in how that intelligence connects to the systems around it.
That is where an MCP (Model Context Protocol) becomes interesting. At a high level, MCP is about giving software a structured way to access tools, data, and external services.
In a financial context, that starts to look less like a technical protocol and more like a new interface layer, one that lets agents interact with wallets, accounts, payments, portfolio data, and other financial actions in a more standardized way. That matters because finance has always been fragmented. Every institution, product, and workflow has its own rules, formats, and integrations. Humans can deal with that fragmentation by clicking, logging in, switching screens, and making judgment calls.
Software agents need something cleaner. MCP could help provide that cleaner layer. Instead of building one-off integrations for every financial action, builders can think in terms of a shared interface between agents and financial systems.
That opens the door to more composable workflows, more automation, and eventually, more autonomous financial behavior. The bigger idea is not that MCP replaces the stack underneath. It is that it creates a more usable front door for intelligence to interact with finance.
And if that works, it changes more than convenience. It changes how financial products are built, how agents operate, and how value moves through the system. That is why MCP as a financial interface layer is worth paying attention to.
It may end up being one of the quiet infrastructure shifts that makes the next generation of finance feel much more usable.
--
The podcasts are authored, edited and produced by Raph Grieco (raphael-grieco.com | olivecapital.vc).