TechPrufer
Get started
Harvey
Harvey logoHarvey · Feature trail

Model Context Protocol (MCP) Integration

2 posts · Dec 2025

What this trail covers

Harvey is adopting the Model Context Protocol (MCP) to enable more flexible and standardized connections between AI systems and external data sources and tools. This allows Harvey to operate as both an MCP client, orchestrating tool calls across external services, and an MCP server, making its capabilities accessible to other systems. This enhances customization, control, and integration with third-party and internal legal tools, while maintaining centralized governance. The platform is also integrating with various legal tools via native APIs and MCP to centralize data and knowledge within Harvey workflows, reducing context fragmentation and manual stitching. The system emphasizes security with rigorous reviews and granular admin controls. MCP connectors enable faster integration.

All Harvey trails
  1. Centralize and Customize Legal Tools With MCPThis post details Harvey's adoption of the Model Context Protocol (MCP) to enhance integration capabilities. It describes how Harvey will function as an MCP client, orchestrating tool calls across external services using a standardized protocol, reducing engineering lift for new integrations and allowing dynamic leverage of partner capabilities. It also explains how Harvey will act as an MCP server, making its legal reasoning capabilities accessible to other systems for embedding into existing workflows, while maintaining centralized permissions, auditing, and ethical walls. The adoption of MCP is presented as a framework for engineering scalable connections that grow with customers, enabling greater customization and control.