# Connect Harvest to Claude Prepare a grounded recorded-hours briefing

> Read time entries with Claude and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.

- Page: https://www.agent200.com/connectors/harvest/framework/claude/
- Connector: [Harvest](https://www.agent200.com/connectors/harvest.md)
- Framework: Claude
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Harvest to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/harvest/framework/claude/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Harvest is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands.
4. The first Harvest request returns an authorization link if the user has not connected Harvest yet: show it to them and continue once they have approved access on Harvest's own page.
5. Check it works with this request: "Review my Harvest time entries for the date range I provide. Use only the selected account and accessible records. Report hours by returned project and task, with any access gaps; do not change entries."
   What should come back:
   - The selected time entry is identified.
   - Only returned entry dates, hours, project and task IDs, and report totals actually returned are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Harvest, then retry.

## Overview

Ask Claude for a focused recorded-hours briefing from one selected time entry. Compare its answer with the retrieved source and separate suggestions from recorded facts.

Start with one identified time entry. Preserve returned entry dates, hours, project and task IDs, and report totals actually returned; report missing data and keep the workflow read-only.

Provider reference: [Harvest API](https://help.getharvest.com/api-v2/timesheets-api/timesheets/time-entries/).

- **Connector:** [Harvest](https://www.agent200.com/connectors/harvest/)
- **Works with:** Claude · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/harvest/framework/claude/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Harvest enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Harvest account.** They approve access once, on Harvest's own page.
- **Claude, with custom MCP servers allowed.** Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

## Connect Harvest to Claude

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Harvest and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open Connectors in Claude

On a Free, Pro, Max or Ultra plan, go to **Customize > Connectors**. On Team or Enterprise, an Owner goes to **Organization settings > Connectors**; members then find the connector under Customize > Connectors.

### Step 3: Add a custom connector

Select **Add**, then **Add custom connector**. Enter a name, Agent200, and the remote MCP server URL, then choose **Continue**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 5: Turn it on in a chat

In a chat, select **+ > Connectors** and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

### Step 6: Connect your Harvest account

The first time you ask Claude for something in Harvest, Agent200 returns an authorization link. Open it and approve access on Harvest's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.

## Test your connection

Ask: "Review my Harvest time entries for the date range I provide. Use only the selected account and accessible records. Report hours by returned project and task, with any access gaps; do not change entries."

What should come back:

- The selected time entry is identified.
- Only returned entry dates, hours, project and task IDs, and report totals actually returned are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected Harvest account, connected role, date range, project permission and pagination. A 403 or empty page does not prove the organization has no time entries.

## Harvest tools Claude can call

- **List time entries** (`harvest_list_time_entries`, read): Find time entries within an explicit date, user or project scope.
- **Read a time entry** (`harvest_get_time_entry`, read): Retrieve one identified time entry and its recorded details.
- **List projects** (`harvest_list_projects`, read): Find projects when the connected role has project-list access.
- **Read a project** (`harvest_get_project`, read): Retrieve one identified project when the connected role permits it.
- **Project time report** (`harvest_time_report_by_project`, read): Read recorded time grouped by project for an explicit date range.
- **Task time report** (`harvest_time_report_by_task`, read): Read recorded time grouped by task for an explicit date range.

## How it works

1. **You ask Claude.** In your own words, for something in Harvest.
2. **Claude picks a tool.** It sees the Harvest tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Harvest connection, within the tools and scopes your project allows.
4. **Claude answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Harvest account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Harvest enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check the selected Harvest account, connected role, date range, project permission and pagination. A 403 or empty page does not prove the organization has no time entries.

## FAQ

### How do I verify this result?

Compare the named time entry and returned entry dates, hours, project and task IDs, and report totals actually returned with the source. Treat missing information as missing, not as a fact.

## Use Harvest with another framework

- [Harvest + ChatGPT](https://www.agent200.com/connectors/harvest/framework/chatgpt.md)
- [Harvest + Claude Code](https://www.agent200.com/connectors/harvest/framework/claude-code.md)
- [Harvest + Muse](https://www.agent200.com/connectors/harvest/framework/muse.md)
- [Harvest + Grok Bot](https://www.agent200.com/connectors/harvest/framework/grok-bot.md)
- [Harvest + OpenAI Dots](https://www.agent200.com/connectors/harvest/framework/openai-dots.md)
- [Harvest + Claude Duet](https://www.agent200.com/connectors/harvest/framework/claude-duet.md)
- [Harvest + Hermes Agent](https://www.agent200.com/connectors/harvest/framework/hermes-agent.md)
- [Harvest + OpenClaw](https://www.agent200.com/connectors/harvest/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
