# How to connect Harvey to Claude

```json
{
  "title": "How to connect Harvey to Claude",
  "toolkit": "Harvey",
  "toolkit_slug": "harvey",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/harvey/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/harvey/framework/claude-cowork.md",
  "updated_at": "2026-11-04T05:31:18.259Z"
}
```

## Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.
This guide walks you through the easiest and most secure way to connect your Harvey account to Claude via Composio Connect, enabling it to list recent audit logs for your organization, find client matters updated this week, search Vault for signed engagement letters, and more such actions on your behalf without compromising your account security.
Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

## Also integrate Harvey with

- [ChatGPT](https://composio.dev/toolkits/harvey/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/harvey/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/harvey/framework/atomic-agent)

## Connect Harvey to Claude Cowork

### Connecting Harvey to Claude Web, Desktop, and Cowork
Two ways to add the Composio connector. Pick whichever you prefer.
### 1. Add with one click
Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.
[Add to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp)
### Add manually
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the Harvey MCP server, and what's possible with it?

The Harvey MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Harvey account. It provides structured and secure access to Harvey's legal AI assistants, Vault documents, client matters, intake requests, audit logs, and usage history, so your agent can run legal AI tasks, search and manage documents, organize client matters, submit intake requests, and track workspace activity on your behalf.
- Legal AI tasks: Have your agent start Harvey agent runs or generate Assistant responses using prompts, documents, knowledge sources, matter context, model selection, and citations.
- Vault document work: Let the agent create and manage Vault projects, upload and search files, check processing status, add files to review tables, and retrieve review results.
- Client and matter management: Direct your agent to create, update, restore, list, or delete Harvey clients and matters, including matter usage information.
- Intake request handling: Instruct your agent to submit Harvey intake requests with documents and check their status, assignment, timestamps, and attachments.
- Activity and usage tracking: Have your agent inspect audit logs and export query or workspace usage history for a selected time period.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `HARVEY_ADD_REVIEW_TABLE_ROW` | Add Review Table Row | Add one processed file or a group of processed files to a Harvey review table and schedule asynchronous review processing. A successful response confirms scheduling, not completion. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_CREATE_AGENT_THREAD` | Create Agent Thread | Start an asynchronous Harvey agent run from a prompt and optional documents. The documented contract and permissions have not been live-verified; use Get Agent Thread with the returned id to retrieve the final result. |
| `HARVEY_CREATE_ASSISTANT_COMPLETION` | Create Assistant Completion | Generate one non-streaming Harvey Assistant response from a prompt with optional documents or knowledge sources, matter attribution, model selection, and citations. This API requires an additional paid workspace purchase. Its documented contract and permissions have not been live-verified. |
| `HARVEY_CREATE_HISTORY_FILE_DOWNLOAD_URLS` | Create History File Download URLs | Create time-limited pre-signed download URLs for file IDs returned by Harvey query-history exports. The URLs grant temporary file access and must be treated as secrets: use them promptly and do not log, publish, or share them. This operation's API-token permission is not specified by Harvey, and the contract has not been live-verified. |
| `HARVEY_CREATE_INTAKE_REQUEST` | Create Intake Request | Submit an idempotent request and optional documents to the Harvey Intake queue. A new request returns HTTP 201 and a replay of the caller-provided idempotency key returns the original request with HTTP 200. This documented contract and its permissions have not been live-verified. |
| `HARVEY_CREATE_VAULT_PROJECT` | Create Vault Project | Create a Harvey Vault project or knowledge base, optionally attributed to a client matter. This documented contract and its permissions have not been live-verified. |
| `HARVEY_DELETE_MATTERS` | Delete Matters | Idempotently soft-delete 1 to 10,000 Harvey matters by firm client and matter identifiers. Inspect deleted, already_absent, and errors even on HTTP 200 because a batch can partially succeed. The parent clients and historical queries remain. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_DELETE_VAULT_FILE` | Delete Vault File | Permanently delete one file from a Harvey Vault project. WARNING: this is a destructive operation and the file cannot be recovered through this action. Harvey may complete deletion asynchronously, so a successful response can confirm acceptance rather than immediate removal. The response preserves any operation or status identifier for follow-up. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_DELETE_VAULT_PROJECT` | Delete Vault Project | Move an entire Harvey Vault project and all its contents to the workspace recycle bin. This is destructive and processing continues asynchronously after Harvey accepts the request, so the response does not prove completion. Confirm the project ID and intended contents before calling. This contract and its permissions are documentation-derived and have not been live-verified. |
| `HARVEY_EXPORT_QUERY_HISTORY` | Export Query History | Export enriched query history for a UTC epoch window of at most 30 days, optionally including related file IDs. Warning: results contain sensitive workspace-wide resource names, prompts, and AI outputs and are not restricted by client-matter or ethical-wall boundaries. Share results and API tokens carefully. Harvey limits History Export endpoints to two requests per minute. This documented contract has not been live-verified. |
| `HARVEY_EXPORT_USAGE_HISTORY` | Export Usage History | Export enriched Harvey workspace usage events for a UTC epoch range of at most 30 days, optionally including related file IDs. The data may contain sensitive resource names across the entire workspace and is not bounded by client-matter or ethical-wall access. Harvey limits History Export endpoints to 2 requests per minute. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_AGENT` | Get Agent | Return metadata for one reachable published Harvey agent. Use this before starting a run to confirm the agent remains available and identify its current published version. This contract is documentation-derived and not live-verified. |
| `HARVEY_GET_AGENT_THREAD` | Get Agent Thread | Read one Harvey agent thread status and any available answer, citations, generated files, or error. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_CURRENT_USER` | Get Current User | Return the Harvey service-user identity associated with the connected API token. Harvey documents this as its authentication-test endpoint but does not document whether it needs a configurable token permission. No no-permission claim is made, and this has not been live-verified. |
| `HARVEY_GET_EARLIEST_AUDIT_LOG` | Get Earliest Audit Log | Return the earliest available Harvey audit log, optionally filtered by log type. Use its ID to begin forward audit-log traversal. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_INTAKE_REQUEST` | Get Intake Request | Read one Harvey Intake request's lifecycle state, assignment, timestamps, and attachments. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_LATEST_AUDIT_LOG` | Get Latest Audit Log | Return the latest available Harvey audit log, optionally for one log type. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_REVIEW_TABLE` | Get Review Table | Return a Harvey review table's title, creation time, and associated file IDs. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_REVIEW_TABLE_ROW` | Get Review Table Row | Return a Harvey review-table row and its cell results for one file. Files in a group resolve to the shared row. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_VAULT_FILES` | Get Vault Files | Return details and processing status for up to 1,000 Harvey Vault file IDs. Files that are missing or inaccessible are returned as records with an error instead of file details. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_GET_VAULT_PROJECT` | Get Vault Project | Return a Harvey Vault project's metadata, file identifiers and names, review tables, and storage limits. This contract, including the provider's unusual HTTP 201 success response for a GET request, is documentation-derived and has not been live-verified. |
| `HARVEY_LIST_AGENTS` | List Agents | List published Harvey agents available to the connected service user, one cursor page at a time. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_LIST_AUDIT_LOGS` | List Audit Logs | Page forward through Harvey audit logs from a starting log ID, optionally filtered by log type. Continuation advances from the last returned log ID. This pagination contract is documentation-derived and has not been live-verified; the inclusive or exclusive boundary behavior must be confirmed to rule out duplicate rows. |
| `HARVEY_LIST_CLIENT_MATTERS` | List Client Matters | Return all Harvey client matters, including deleted records and usage statistics. This unpaginated contract is documentation-derived and has not been live-verified. |
| `HARVEY_LIST_RECYCLED_VAULT_PROJECTS` | List Recycled Vault Projects | List Vault projects currently in the workspace recycle bin, optionally filtered by project-name text or client matter. Results retain Harvey's newest-deletion-first order. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_LIST_VAULT_PROJECT_FILES` | List Vault Project Files | List, filter, and sort files in a Harvey Vault project, one cursor page at a time. The response and pagination contract is documentation-derived and has not been live-verified. |
| `HARVEY_LIST_VAULT_PROJECTS` | List Vault Projects | List and filter workspace Vault projects and knowledge bases, one page at a time. The response and pagination contract is documentation-derived and has not been live-verified. |
| `HARVEY_LIST_VAULT_PROJECT_USERS` | List Vault Project Users | List workspace users with direct or inherited effective access to a Harvey Vault project. The project owner is included with MANAGE access, and provider-returned access-origin, inherited-access, and owner indicators are preserved when present. Requires Vault API plus either Vault sharing (view only) or Vault sharing permission. This response contract and permission behavior are documentation-derived and have not been live-verified. |
| `HARVEY_REMOVE_VAULT_PROJECT_USERS` | Remove Vault Project Users | Remove direct WORKSPACE_USER shares from a Harvey Vault project by email. Inherited access through workspace, group, or space shares remains effective. Inspect both removed and failed because individual emails can fail without rejecting the entire request. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_SEARCH_AUDIT_LOGS_BY_TIME` | Search Audit Logs by Time | Return the first Harvey audit log at or after a UTC epoch timestamp, optionally filtered by log type. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_SEARCH_VAULT` | Search Vault | Return semantically relevant document chunks from one Harvey Vault project. The response is ordered by relevance and can optionally include source file names. This contract has not been live-verified. |
| `HARVEY_UPDATE_VAULT_PROJECT_USERS` | Update Vault Project Users | Add workspace users or update their direct access level on a Harvey Vault project. This is an additive partial update: users omitted from the request remain unchanged, and the project owner must not be included. Inspect failed even on HTTP 200 because individual user updates can fail. This contract and its permissions are documentation-derived and have not been live-verified. |
| `HARVEY_UPLOAD_VAULT_FILES` | Upload Vault Files | Upload up to 50 new or replacement files to a Harvey Vault project. Optional Vault paths correspond positionally to the uploaded files, and duplicate_mode controls filename collisions. The provider returns HTTP 201. This documented contract and its permissions have not been live-verified. |
| `HARVEY_UPSERT_CLIENTS` | Upsert Clients | Create, update, or restore up to 10,000 Harvey clients by firm client identifier. Always inspect the returned errors array because Harvey can report row-level failures alongside successful rows in HTTP 200 responses. This contract is documentation-derived and has not been live-verified. |
| `HARVEY_UPSERT_MATTERS` | Upsert Matters | Create, update, or restore up to 10,000 Harvey matters under existing clients. Inspect errors even on HTTP 200 because valid rows can succeed while other rows fail. The connected API token needs Harvey's Client matters admin (write:client_matters) permission; sending allowed on any row additionally needs use:disallowed_client_matters. These are Harvey API-token permissions, not OAuth scopes. This contract and its permissions are documentation-derived and have not been live-verified. |

## Supported Triggers

None listed.

## Troubleshooting

### 1. Why does Claude not use the Composio connector for Harvey?

The connector can show as connected, but Claude must use it in each Harvey conversation.
- Click + at the lower left of the chat, or type /.
- Hover Connectors.
- Turn on Composio.
- Ask Claude to connect to Harvey again.

### 2. Why does Claude show an MCP server error before Harvey connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Harvey.
- Check that the connector URL is https://connect.composio.dev/mcp.
- Connectors run from Anthropic's cloud, so your device network is usually not the problem.
- Add the connector again from Customize > Connectors, then ask Claude to connect Harvey.
- If it fails again, send the error and the ofid_ reference id to support@composio.dev.

### 3. Why does the Harvey authorization link not work?

The Composio connector is one server. Your Harvey account connects separately when Claude asks for it.
- If the browser does not open, or the link expires, ask Claude to retry the Harvey connection.
- Composio creates a fresh Harvey authorization link.
- Open that link in your browser and finish the Harvey sign-in.

### 4. Why do Harvey actions fail after they worked before?

The Harvey connection can expire or lose permission.
- Ask Claude to inspect the Harvey connection.
- If the connection is unhealthy, disconnect it when Claude prompts you.
- Reconnect the Harvey account and retry the action.
- If Claude shows a permission prompt, approve it before Claude changes data in Harvey.
- If the action still fails with a permission error, check that the connected account has that permission in Harvey itself.

### 5. How do I switch to a different Harvey account?

Claude can manage the Harvey connection for you.
- Ask Claude to disconnect or delete the current Harvey account.
- Ask Claude to connect Harvey again.
- Open the new Composio authorization link for Harvey.
- Sign in with the other Harvey account in the browser.
- After the account connects, ask Claude to retry the Harvey task.

### 6. Why is my Harvey connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Harvey connection works in Claude Web, Desktop, and Cowork.
- In Claude Desktop, open Customize > Connectors.
- Next to Composio, click ⋮ and click Clear cache.
- If Harvey tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
- On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Harvey.

## Creating MCP Server - Stand-alone vs Composio SDK

The Harvey MCP server connects Claude Web, Desktop, and Cowork to your Harvey account through Composio. Once connected, Claude can use the available Harvey tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build Harvey MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/harvey/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/harvey/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/harvey/framework/atomic-agent)

## Related Toolkits

- [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.
- [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service.
- [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows.
- [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow.
- [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows.
- [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application.
- [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities.
- [AltTextLab](https://composio.dev/toolkits/alt_text_lab) - AltTextLab is an AI service that generates accessible, SEO-aware alt text for images. It helps teams make image content easier to understand, index, and publish.
- [Anthropic administrator](https://composio.dev/toolkits/anthropic_administrator) - Anthropic administrator is an API for managing Anthropic organizational resources like members, workspaces, and API keys. It helps you automate admin tasks and streamline resource management across your Anthropic organization.
- [Api labz](https://composio.dev/toolkits/api_labz) - Api labz is a platform offering a suite of AI-driven APIs and workflow tools. It helps developers automate tasks and build smarter, more efficient applications.
- [Apiframe](https://composio.dev/toolkits/apiframe) - Apiframe is an API platform for generating and managing AI images, videos, music, uploads, assets, jobs, and custom LoRAs. It gives developers one clean API for creative AI workflows without juggling multiple model providers.
- [Apipie ai](https://composio.dev/toolkits/apipie_ai) - Apipie ai is an AI model aggregator offering a single API for accessing top AI models from multiple providers. It helps developers build cost-efficient, latency-optimized AI solutions without juggling multiple integrations.
- [Arize AX](https://composio.dev/toolkits/arize_ax) - Arize AX is an AI engineering platform for tracing, evaluating, and improving AI applications. Use it to debug LLM behavior, compare experiments, and improve production AI quality.
- [Artificial Analysis](https://composio.dev/toolkits/artificial_analysis) - Artificial Analysis is an independent benchmarking platform for AI models and API providers. Use it to compare model intelligence, coding, math, pricing, latency, throughput, and arena rankings.
- [AssemblyAI](https://composio.dev/toolkits/assemblyai) - AssemblyAI is a speech-to-text and audio intelligence API for uploaded or hosted media. Use it to turn audio and video into accurate transcripts, summaries, and insights.
- [Astica ai](https://composio.dev/toolkits/astica_ai) - Astica ai provides APIs for computer vision, NLP, and voice synthesis. Integrate advanced AI features into your app with a single API key.
- [Avoma](https://composio.dev/toolkits/avoma) - Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence. It helps teams turn conversations into searchable notes, follow-ups, coaching insights, and revenue intelligence.
- [Bigml](https://composio.dev/toolkits/bigml) - BigML is a machine learning platform that lets you build, train, and deploy predictive models from your data. Its intuitive interface and robust API make machine learning accessible and efficient.
- [Black Forest Labs](https://composio.dev/toolkits/bfl) - Black Forest Labs provides hosted FLUX models for generating and editing images and videos. It offers fast, flexible media creation with asynchronous processing and fine-tuning support.
- [Bland AI](https://composio.dev/toolkits/bland_ai) - Bland AI is a conversational AI platform for building voice agents, phone calls, messaging, and communication workflows. Use it to automate calling, evaluate conversations, and run voice operations at scale.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Harvey MCP?

With a standalone Harvey MCP server, the agents and LLMs can only access a fixed set of Harvey tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Harvey and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Harvey tools.

### Can I manage the permissions and scopes for Harvey while using Tool Router?

Yes, absolutely. You can configure which Harvey scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Harvey data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)