Harvey

Ask legal questions, query Vault projects and search research knowledge sources.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Harvey connector does

The Harvey MCP server connects Harvey, a legal AI platform used by law firms and in-house legal teams, to Claude, Google Gemini and Microsoft 365 Copilot. It exposes five read-only tools: ask a general legal question, ask about documents in a Vault project, query a research knowledge source, and list the projects and sources you can reach. Sign-in is OAuth.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Harvey tools (5)

  • Ask Harvey
  • Ask Harvey About Vault Project
  • Ask Harvey With Knowledge Source
  • List Vault Projects
  • List Knowledge Sources

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Harvey states its output is not legal advice. Its Platform Agreement describes the service as a research tool whose output is AI-generated and "may contain errors and misstatements or may be incomplete". That disclaimer is the vendor's own and applies to answers reaching you through an assistant exactly as it does in Harvey's own interface.
  • No application scopes exist. Harvey's RFC 9728 resource descriptor declares no scopes_supported, and the Auth0 tenant it delegates to advertises fourteen scopes that are all OpenID identity claims. Nothing at the OAuth grant separates a general legal question from a query against a specific client's documents.
  • Access is gated twice, per account and per tool. Enrolment in the hosted MCP feature is arranged with Harvey rather than enabled by the user, and the Vault tool additionally requires the VAULT permission. Harvey also states elsewhere that API access to its Assistant requires an additional purchase, so entitlement is not uniform across workspaces.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or annotation state is published here.
  • Every call is stateless. Harvey states the server maintains no conversation history between requests, so multi-turn workflows depend entirely on the client re-sending context.
  • Confidentiality ends at Harvey's boundary. Harvey's ethical wall enforcement governs access within Harvey. Its MCP guide states Harvey is not responsible for third-party handling of data once it leaves, so retrieved privileged content is governed by your agreement with the assistant vendor from that point on.
  • Matter attribution through the connector is unresolved. Harvey's completion API accepts a client-matter identifier and Harvey documents client matters as an access-scoping mechanism, but no MCP tool documents such a parameter. We could not establish whether connector queries are attributable to a matter.
  • Rate limits are documented for the REST API, not for MCP. Harvey publishes per-minute limits by endpoint category — 20 for the Assistant completion endpoint and 10 for Vault endpoints, applied per organization — and returns HTTP 429 when exceeded. Harvey publishes no MCP-specific limit, and we did not test whether these apply to connector traffic.
  • Regional deployments use different hosts. Harvey documents EU and Australian API hosts for customers on those deployments. The connector endpoint Anthropic lists is the US host, and Harvey does not document a regional MCP endpoint.

Frequently asked questions

Can the Harvey connector delete a Vault project or a document?

No. All five tools ask questions or list what exists, and none carries a create, upload, update or delete verb. Harvey's Vault API does document deleting a file and deleting an entire project, and states that project deletion cannot be undone, but neither endpoint is exposed as an MCP tool. The connector reads; it does not manage documents.

What client documents can the Harvey MCP server read?

Only the Vault projects your own Harvey account can already open. Harvey states the server resolves every request to the authenticated user and enforces that user's permissions and feature gates, so Vault queries are scoped to projects you can access. The connector grants no new reach into the workspace, but everything you can reach it can read.

Does connecting Harvey to Claude break privilege or an ethical wall?

Harvey enforces walls inside Harvey, not after the answer leaves. Harvey states it syncs and enforces your firm's existing ethical wall policies and never creates or modifies walls. Its MCP guide separately states that data sent to third-party assistants is governed by your agreements with those providers and that Harvey is not responsible once data leaves its systems.

What OAuth permissions does the Harvey MCP server request?

None that narrow anything. Harvey's resource descriptor omitted scopes_supported entirely on 2026-08-22, and the Auth0 tenant behind it advertised fourteen scopes that are all OpenID identity claims such as openid, profile and email. No scope separates asking a general legal question from querying a specific client's Vault project.

Why does my Harvey connector say the hosted MCP server is not enabled?

Because the feature is enabled per account rather than self-serve. Harvey's troubleshooting section directs you to your Harvey admin or representative to confirm you are enrolled. A separate message, that you lack permission to use a tool, is a different problem: Harvey states ask_about_vault requires the VAULT permission on your account specifically.

Does the Harvey MCP server remember earlier questions in the conversation?

No. Harvey states each tool call is stateless and the server keeps no conversation history between requests. Your MCP client has to carry context across calls itself. That matters for follow-ups, because a second question about the same Vault project must repeat the project identifier rather than relying on the server to recall it.

Can two lawyers at the same firm share one Harvey MCP connection?

No, and Harvey designed it that way. Harvey states each user authenticates individually through the browser OAuth flow, and the server resolves each request to that authenticated user before enforcing their permissions. There is no shared workspace token for the connector, so one person's access never becomes another's.

Can I use the Harvey MCP server with Claude Code?

Not through the documented setup. Harvey lists Claude Web, Claude Desktop, Google Gemini and Microsoft 365 Copilot, and its own authorization metadata advertised no registration_endpoint on 2026-08-22. Clients that rely on Dynamic Client Registration have nothing to register against. Harvey documents no personal access token fallback for MCP either.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Harvey to work.

Connect Harvey once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio