Harvest
Overview
Section titled “Overview”The Harvest integration connects Monday Morning to your Harvest time tracking account, giving your agent access to time entries, budget performance, profitability metrics, and team utilization data. This enables workflows like checking budget burn during planning or reviewing team capacity before dispatching work.
Tool Group
Section titled “Tool Group”All six Harvest tools belong to the opt-in harvest tool group. They are not listed in the agent’s tool catalog until you opt in via the Monday Morning server entry in .mcp.json:
"env": { "MM_TOOL_GROUPS": "harvest" }The tools still dispatch by name even when not listed — opting in only makes them visible in tools/list.
Prerequisites
Section titled “Prerequisites”- A Harvest account with time tracking data
- A Harvest Personal Access Token and Account ID from id.getharvest.com/developers
- The Monday Morning desktop app (Harvest calls are proxied through it)
Step 1: Create a Personal Access Token
Section titled “Step 1: Create a Personal Access Token”- Go to id.getharvest.com/developers
- Create a Personal Access Token and copy it
- Note your Account ID, shown alongside the token on the same page
Step 2: Configure in Monday Morning
Section titled “Step 2: Configure in Monday Morning”In the desktop app, open the Harvest plugin’s settings (Settings → Plugins, then Configure on the Harvest row) and enter the Personal Access Token and Account ID. Credentials are stored encrypted on the device, and a Test control verifies them against the Harvest API.
Then link the project: Settings → Integrations → Harvest is an inline row where you pick the Harvest project this workspace tracks time against. The ID is saved to .mm/plugins/harvest/config.json.
Step 3: Verify the Connection
Section titled “Step 3: Verify the Connection”Ask your agent to list your Harvest projects:
List my active Harvest projectsThe agent will call mm_harvest_list_projects. If configured correctly, you will see your Harvest projects listed.
Available Tools
Section titled “Available Tools”| Tool | Description |
|---|---|
mm_harvest_list_projects | List all projects from Harvest, optionally filtered by active status. |
mm_harvest_list_time_entries | List time entries, optionally filtered by project, user, and date range. |
mm_harvest_aggregate_time | Aggregate time entries, grouped by user, task, or date. |
mm_harvest_compute_budget_performance | Compute budget performance metrics — actual hours versus budgeted hours. |
mm_harvest_compute_profitability | Compute profitability metrics including revenue, costs, and margins. |
mm_harvest_compute_utilization | Compute team or individual utilization rates from time entries. |
The MCP-side handlers for these tools are thin stubs — actual Harvest API calls are proxied through the desktop app’s Rust backend, which resolves the stored credentials itself.
Common Workflows
Section titled “Common Workflows”Check budget burn for a project
Section titled “Check budget burn for a project”How much of our budget have we used on the API redesign project?The agent calls mm_harvest_compute_budget_performance to compare actual hours against the budgeted amount.
Review team utilization
Section titled “Review team utilization”What is our team's utilization rate for the past two weeks?The agent calls mm_harvest_compute_utilization with a date range to show how much of available time is being billed.
Get a time breakdown by task
Section titled “Get a time breakdown by task”Show me time entries for this project grouped by task for the past monthThe agent calls mm_harvest_aggregate_time with group_by: "task" and the appropriate date range.
Assess project profitability
Section titled “Assess project profitability”What are the profitability margins on the current project?The agent calls mm_harvest_compute_profitability to calculate revenue, costs, and margin percentages.
Troubleshooting
Section titled “Troubleshooting”“Use the Harvest MCP proxy via Tauri commands” error The tool call reached the MCP stub handler instead of the desktop proxy. Run the request through the desktop app, and verify the Harvest credentials pass the Test check in the plugin’s settings.
The agent says it can’t see the mm_harvest_* tools
The harvest group is not opted in. Add "MM_TOOL_GROUPS": "harvest" to the server’s env in .mcp.json — or ask the agent to call the tool by its exact name; delisted tools still dispatch.
No projects returned Verify that your Harvest account has active projects and that the token and Account ID belong to the correct Harvest account.
Time entries missing
Check the date range parameters. Use explicit from and to dates (YYYY-MM-DD) to widen the range.
Budget data showing zero Budget tracking must be enabled on the Harvest project. Go to Harvest → Projects → (your project) → Edit and ensure a budget is set.