How to Connect Claude to Harvey AI via MCP

Prerequisites

• An active Harvey account — this is a customer feature, not a free tier
• An MCP client that supports remote servers over Streamable HTTP with OAuth. Claude, Google Gemini, and Microsoft 365 Copilot are the clients Harvey names. A client that only speaks stdio will not work.
• Feature enrollment on your tenant. Harvey's documentation is explicit that you should check with your Harvey admin or representative to confirm you are enrolled. We expect an unenrolled account to fail at sign-in rather than at config time, though we have not tested that directly.
• Role permissions per tool. Vault tools require the Vault permission on your Harvey role, so two users at the same firm can see different tool lists.
• Requires Harvey subscription. Contact sales for pricing.

1. Get your tenant enrolled

Ask your Harvey admin or representative to enable MCP access for your account and to confirm which knowledge sources and Vault projects your role can reach. Do this before touching any client configuration. Two of the four failures listed under Troubleshooting look like client bugs and are not. They are entitlements nobody turned on, and no amount of config editing will reach them.

2. Add the server in your client

Harvey supplies the connection details with your enrollment rather than publishing them. Use the endpoint your admin or representative gives you, set the transport to HTTP, and let the client handle the OAuth handshake. We deliberately do not print a URL here — a guessed endpoint fails silently on most clients, which is worse than having none. Harvey's current documentation is at https://developers.harvey.ai/guides/harvey_mcp.

3. Authenticate

The first tool call opens a browser sign-in against your Harvey account. Approve it there and the client stores the session. There is no static API key to paste and none to rotate. Access follows your Harvey user, so removing someone in Harvey removes their route to MCP as well.

4. The tools you can call

Harvey MCP exposes 5 tools. Knowing the names is useful for prompting: you can tell Claude which one to reach for instead of hoping it picks correctly.

ask_harvey

Answers general legal questions from Harvey's legal knowledge, without pointing at a specific document.

ask_with_knowledge_source

Runs the same question flow, scoped to a named research database — the UK tax law source, for example.

list_knowledge_sources

Enumerates which research databases your account can reach. Worth calling first; the list is entitlement-dependent.

list_vault_projects

Lists the Vault projects visible to you. Requires the Vault permission on your Harvey role.

ask_about_vault

Answers questions against the documents inside a Vault project, with source citations.

5. Test it

Call list_knowledge_sources first. It is the cheapest way to prove the whole chain works — enrollment, OAuth, and tool routing — and it returns your entitlements, so you learn what your role can reach at the same time. A list of sources means the chain is working. An empty list also means it is working, and that your role has no sources attached — an entitlement problem, not a connection one.