Back to MCP directory
publicPublicdnsLocal runtime

harvest-mcp-server

为 Harvest 启用自然语言时间跟踪和报告功能,包括自动请假申请、项目/任务匹配和日期解析。

article

README

Harvest Natural Language Time Entry MCP Server

An MCP server that lets you log Harvest time entries using natural language, including special handling for leave requests. This server makes time tracking more intuitive by understanding natural language inputs and automatically handling common scenarios like leave requests.

Features

  • 🗣️ Natural language time entry parsing
  • 🏖️ Special leave request handling (e.g., "I'm off sick today")
  • ⏰ Configurable work day hours
  • 🌍 Timezone support
  • 🎯 Automatic project and task matching
  • 📅 Smart date parsing (today, yesterday, etc.)

Prerequisites

  • Node.js installed
  • A Harvest account
  • Personal access token from Harvest Developer Tools
  • Account ID (shown on the same page as your token)

Installation

Installation

  1. Install the Claude desktop app

  2. Clone this repository:

git clone https://github.com/adrian-dotco/harvest-mcp-server.git
cd harvest-mcp-server
  1. Install dependencies and build:
npm install
npm run build
  1. Run the setup script:
node build/setup.js
  1. Follow the prompts to enter your:

    • Harvest Personal Access Token (from https://id.getharvest.com/developers)
    • Harvest Account ID
    • Standard work day hours (default: 7.5)
    • Timezone (default: Australia/Perth)
  2. Restart Claude desktop app

That's it! You can now use natural language time tracking in Claude.

Staying Updated

To update to the latest version:

git pull
npm install
npm run build

The setup script will have configured Claude to use your local build of the server, so any updates you pull will be automatically available after rebuilding.

Usage

The server provides several tools for interacting with Harvest:

log_time

Log time entries using natural language. Examples:

Regular time entries:

"2 hours on Project X doing development work today"
"45 minutes on Project Y testing yesterday"
"3.5 hours on Project Z meetings last Friday"

Leave requests (automatically uses standard work day hours):

"I'm off sick today"
"I'm unwell today"
"Taking annual leave next week"

get_time_report

Get time reports using natural language queries. Examples:

  1. Time Period Options:
"Show time report for last month"
"Get time summary for this week"
"Show hours from January 1st to January 31st"
"Report time for Q1"
"Show me yesterday's hours"
  1. Report Types:
  • By Project (default):
    "Show time report for last month"
    "Get project hours for this week"
    
  • By Client:
    "Show time report by client for this month"
    "Get hours by client for Q1"
    
  • By Task:
    "Show time summary by task for January"
    "Get task breakdown for last week"
    
  • By Team Member:
    "Show team hours for last week"
    "Get time report by user for this month"
    
  1. Report Details: Each report includes:
  • Total hours worked
  • Billable vs non-billable hours
  • Billable amounts (if you have permission)
  • Project/client/task/user details based on report type

list_projects

List all available Harvest projects:

List my projects

list_tasks

List available tasks for a specific project:

Show tasks for Project X

list_entries

View recent time entries:

Show my recent time entries

Configuration

The server supports these environment variables:

  • HARVEST_ACCESS_TOKEN: Your Harvest personal access token
  • HARVEST_ACCOUNT_ID: Your Harvest account ID
  • STANDARD_WORK_DAY_HOURS: Default hours for a full work day (default: 7.5)
  • TIMEZONE: Your timezone (default: Australia/Perth)

Development

The server is built using:

  • TypeScript
  • MCP SDK
  • chrono-node for natural language date parsing
  • Harvest API v2

To contribute:

  1. Fork the repository
  2. Create a feature branch
  3. Submit a pull request

License

MIT License - see LICENSE for details

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client