Harvest FAQs

Question 1

How does harvest-mcp enhance Harvest API interactions?

Accepted Answer

harvest-mcp offers critical operations often missing in other Harvest MCP implementations, such as updating, deleting, and restarting time entries and timers. This provides a more complete and powerful interface for managing your work data.

Question 2

What key functionalities does harvest-mcp offer?

Accepted Answer

It provides extensive capabilities including full CRUD (Create, Read, Update, Delete) operations for time entries, advanced timer controls (start, stop, restart), and detailed retrieval of project, client, task, and user information within your Harvest account.

Question 3

Can harvest-mcp be integrated with Claude Code?

Accepted Answer

Yes, harvest-mcp is designed for easy integration with Claude Code. You can configure it by adding specific details like the command path and environment variables for your Harvest API credentials to your `~/.claude.json` file.

Question 4

What are the requirements to use harvest-mcp?

Accepted Answer

To run harvest-mcp, you will need Bun v1.0 or later installed, along with a Harvest account and a Personal Access Token for authentication with the Harvest API.

Question 5

What is harvest-mcp?

Accepted Answer

harvest-mcp is a Model Context Protocol (MCP) server built with Bun and TypeScript, designed to provide comprehensive programmatic control over the Harvest time tracking API. It allows for managing time entries, projects, clients, tasks, and users.

Harvest

Harvest

Características Principales

Casos de Uso

Características Principales

Casos de Uso