Connecting MCP Servers to Harvey
Learn how your MCP server can connect to Harvey for customers to power end-to-end legal work.
Last updated: Aug 20, 2026
Overview
Harvey supports MCP (Model Context Protocol), an open standard that allows external tools and data sources to connect directly into Harvey through two different paths:
- Partner MCP Submissions: Partners can submit their MCP server to be considered for Harvey’s Connector Library.
- Bring-Your-Own-MCP (BYOMCP) for Harvey Customers: Workspace administrators can connect a firm-built MCP server for use within their own Harvey workspace.
These paths have different review and security responsibilities.
Partner MCP Submissions
As a partner, you can build and integrate an MCP server that users can use without leaving Harvey, helping them work more efficiently across various legal tasks such as:
- Researching specific legal content to synthesize in drafting
- Searching and updating files and contracts
- Embedding preferred data, formats, and visualizations in documents
Harvey is used by over 140K+ legal professionals across 1,500+ law firms and in-house legal teams worldwide. Joining Harvey’s MCP Connector Library puts your tool directly inside the workflows where lawyers do their core work without requiring them to leave Harvey or switch context.
Harvey acts as the client to retrieve user credentials, make requests to your server, and surface the response inside Harvey's interface. A workspace administrator must explicitly enable your connector before any user in their organization can connect to it within Harvey.
Enabling Your Connector
To join Harvey’s MCP Connector Library, fill out this form. We’ll ask that you submit information regarding how your tool operates and is built, including security protocols, for us to review.
How the Connection Works
Once a workspace admin enables your connector within Harvey, users can authenticate with your service to connect their accounts. Harvey handles the authentication handshake, stores the user's token securely, and routes requests to your server on their behalf.
Authentication Requirements
Harvey implements the MCP Authorization Specification (2025-11-25). Harvey recommends your MCP server supports the following:
Requirement | Details |
|---|---|
OAuth 2.1 with PKCE (S256) | Required. Harvey uses PKCE for all authorization flows. Your server must support the S256 code challenge method. |
RFC 8414 — AS Metadata | Required. Harvey fetches your server's OAuth metadata before initiating any login. Publish a valid metadata document at the standard well-known endpoint. |
RFC 9728 — PRM Discovery | Required. Harvey verifies your declared authorization server before proceeding. |
HTTPS | Required. Harvey rejects any connector URL not using HTTPS. |
RFC 7591 — Dynamic Client Registration | Optional. If supported, Harvey will auto-register itself as an OAuth client, simplifying setup. |
Data Handling
Harvey's controls cover authentication, token storage, access scoping, and audit logging within Harvey. Once data reaches your MCP server, it is subject to your own privacy policy, data handling practices, and customer agreements.
Relevant Platform Behavior
Harvey's MCP client is actively evolving. The following details are relevant when designing your integration:
Harvey Behavior | What It Means |
|---|---|
Runtime write-action confirmation | Due to the evolving state of MCP technology, Harvey may not prompt users before a connected tool executes certain types of write actions in both Harvey and the relevant third party application(s). Partners should design write access scope carefully and consider implementing the minimum write scope required for intended user functionality. Harvey will assess your holistic security posture as part of evaluating Connector Library partners. |
End user disclosure at connect time | Individual users may only be shown the read vs. write operations your connector can perform to the extent described in MCP documentation. Partners should consider having clear admin documentation so that Harvey customer admins can properly assess the full feature set. |
Token revocation not automatic | Admins disconnecting the MCP server in Harvey wipes the stored access token but does not call your identity provider's revocation endpoint. If you require immediate revocation, surface a revocation flow on your side as well. |
Bring Your Own MCP Server [Early Access]
Bring Your Own MCP Server (BYOMCP) allows a workspace administrator to connect a custom MCP server to Harvey for use within their Harvey workspace.
How BYOMCP Works
Two steps are required before Harvey sends data to a custom MCP server:
- A workspace administrator enables the server for the workspace.
- Each user separately completes the OAuth flow for their own account.
Harvey does not make MCP requests on behalf of users who have not personally authenticated.
Understand the Risks Before Enabling a Custom MCP
Depending on its design and permissions, an MCP server may:
- Receive confidential information from Harvey.
- Read, create, modify, send, or delete data.
- Trigger actions in external services or delegate work to other agents.
- Request overly broad OAuth permissions.
- Log, retain, share, or process data outside your organization’s required locations.
- Expose data if it does not properly isolate users or workspaces.
- Change behavior when its code, dependencies, or tools are updated.
Review the server’s tools, permissions, hosting, security practices, and data-handling terms before enabling it.
Your Responsibilities
Harvey’s controls apply up to the point where a request leaves Harvey. After that, the MCP server owner controls how data is processed, logged, retained, shared, and secured. Before enabling a custom MCP server, confirm that it:
- Uses HTTPS and OAuth 2.1 with PKCE (S256), where authentication is required.
- Requests only the permissions necessary for its intended tools.
- Enforces user and workspace-level authorization.
- Validates token audiences and does not pass Harvey tokens to other services.
Review Third-Party MCP Servers Before Connecting Them
If your firm did not build and fully control the MCP server, we recommend submitting it to Harvey for security review before connecting it. Harvey may not be able to technically prevent an administrator from connecting a server without review, and connecting a server does not mean that Harvey has reviewed or approved it.
Relevant BYOMCP Platform Behaviors
- Harvey may not be able to prompt users before a customer's custom MCP performs a write, delete, send, or delegated action. Do not rely on a Harvey user confirmation as a safety control.
- Harvey does not continuously monitor custom MCP servers or proactively review every tool, dependency, or update. Customers are responsible for validating the security and performance of the MCP servers they submit and connect to their Harvey workspace.
- Your organization is responsible for re-evaluating the MCP server when its tools, permissions, dependencies, hosting, or data-handling practices change.
- When Admins disconnect a MCP server, its stored access token is removed from Harvey but the token may not be revoked from the identity provider. Also note that disconnecting a MCP server will not automatically delete any of the data previously submitted to the server.
Additional Information
If you're a partner who would like more information about listing your MCP connector in Harvey, you can reach out to our Partnerships team at partnerships@harvey.ai.
Was this article helpful?