Model ML Now Supports MCP
3 MIN. READ
Model ML has adopted the Model Context Protocol (MCP), creating a standardized way for firms to connect their data, systems, and AI tools.
Why MCP?
The benefits:
Connect market data, document management systems, CRMs, and internal databases through a common framework.
Make firm data available directly within Model ML agents and workflows.
Access Model ML’s financial intelligence from MCP-compatible tools such as Claude, Copilot, or internally developed agents.
Reduce the need to build and maintain separate point-to-point integrations for every system.
The considerations:
MCP connections still require appropriate permissions, governance, and security controls.
Data quality and usability depend on how the underlying system is structured and maintained.
Firms need to define clearly which agents can access which data and what actions they are permitted to take.
How Model ML Has Adopted MCP
Model ML supports MCP natively in both directions:
Bring data and tools into Model ML. Firms can connect external systems, including licensed market data from LSEG and internal data held in Snowflake, to power research, analysis, monitoring, and deliverables.
Make Model ML available elsewhere. Teams can call Model ML’s agents and financial intelligence from any MCP-compatible environment, including third-party assistants and tools built by their own engineers.
Because the framework is standardized, firms are not limited to a predefined integration list. Any organization can add its own MCP server and make proprietary systems, data sources, and tools available within Model ML, subject to its existing access and security policies.
If your firm is developing an agent strategy, MCP provides a practical framework for connecting it to Model ML without forcing your teams to replace the systems they already use.
