Harvest MCP Server

What is Harvest MCP Server?

Harvest MCP Server is a server that provides tools for interacting with the Harvest time tracking API via the Model Context Protocol. It is intended for users who want to manage Harvest time entries, projects, and tasks programmatically through an MCP client such as Claude Desktop.

How to use Harvest MCP Server?

Install and run the server using Docker. For Claude Desktop, add a configuration entry with the docker command and set the HARVEST_ACCOUNT_ID and HARVEST_TOKEN environment variables. For other MCP clients, pull the Docker image from Docker Hub (tommcl/harvest-mcp) or build it locally from the repository.

Key features of Harvest MCP Server

• Retrieve authenticated user information (get_current_user)
• List, get, create, update, delete, and restart time entries
• Create time entries via duration or start/end times
• Stop running time entries
• Delete a time entry’s external reference
• List projects and tasks with optional filtering

Use cases of Harvest MCP Server

• Automatically log time entries into Harvest from an MCP-enabled chat interface
• Query and update existing time entries without switching apps
• Manage project and task lists as part of a time tracking workflow
• Integrate Harvest time tracking into AI‑driven assistant conversations

FAQ from Harvest MCP Server

What tools does Harvest MCP Server provide for time entries?

It provides list_time_entries, get_time_entry, create_time_entry, create_time_entry_via_start_end, update_time_entry, delete_time_entry, delete_time_entry_external_reference, restart_time_entry, and stop_time_entry.

What are the prerequisites for using Harvest MCP Server?

You need Docker and a Harvest account with API credentials (Personal Access Token and Account ID).

How do I obtain Harvest API credentials?

You can get your Personal Access Token and Account ID from the Harvest Developer Tools page.

How is the server deployed?

It is deployed as a Docker container. You can pull the pre‑built image from Docker Hub (tommcl/harvest-mcp) or build it locally from the repository.

Does the server require any authentication?

Yes, the environment variables HARVEST_ACCOUNT_ID and HARVEST_TOKEN must be set with valid Harvest API credentials.