Centralize and Customize Legal Tools With MCP

This 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.