mcpField
H
Harvest Time Tracking MCP Server

Harvest Time Tracking MCP Server

Local
getharvest.comProductivity1Updated 31w ago

About Harvest Time Tracking MCP Server

Harvest Time Tracking MCP Server lets LLM clients access Harvest account data and manage time entries. Its tools cover company, client, project, user, task assignments, and time-entry lookup and creation.

Key features

  1. 01Retrieve company information
  2. 02Search and inspect clients and projects
  3. 03List users and project assignments
  4. 04Search and retrieve time entries
  5. 05Create time entries

Use cases

  1. 01Review client and project details
  2. 02Check project users and task assignments
  3. 03Find time entries by date or account filters
  4. 04Record hours against a project task

MCP support

Exposes Harvest account operations as MCP tools, including lookups for company, clients, projects, users, and time entries, plus time-entry creation.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"harvest": {
"command": "npx",
"args": [
"-y",
"@harvest/mcp-server-typescript"
],
"env": {
"HARVEST_ACCOUNT_ID": "<HARVEST_ACCOUNT_ID>",
"HARVEST_ACCESS_TOKEN": "<HARVEST_ACCESS_TOKEN>",
"HARVEST_BASE_URL": "<HARVEST_BASE_URL>"
}
}
}
}
Run commandnpx -y @harvest/mcp-server-typescript
Environment variables to set
HARVEST_ACCOUNT_ID
HARVEST_ACCESS_TOKENSecret
HARVEST_BASE_URL

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@harvest/mcp-server-typescript

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Harvest Time Tracking MCP Server

npm version

A TypeScript based MCP (Model Context Protocol) server for Harvest time tracking app enabling LLM clients to interact with Harvest account.

Installation

npx -y @mayankg0324/mcp-server-harvest

Prerequisites

  • Node.js >= 18 (or Bun Runtime for development)
  • Harvest account with API access
  • API Personal Access Token from Harvest
  • Account ID from Harvest

More details on how to create a Personal Access Token can be found in the Harvest API documentation.

Available Tools

ToolDescriptionInputsOutput
get-companyGet company informationNoneCompany Information (Name, URL, ID and Currency)
search-clientsSearches for clients• name: string (optional) - Client name
• isActive: boolean (optional) - Active status
List of clients with IDs and details
get-clientGet client information• clientId: string - Client IDDetailed client information
search-projectsSearches for projects• name: string (optional) - Project name
• clientId: string (optional) - Client ID
• isActive: boolean (optional) - Active status
List of projects with IDs and details
get-projectGet project information• projectId: string - Project IDDetailed project information
list-usersLists all usersNoneList of users with IDs and details
get-userGet user information• userId: string - User IDDetailed user information
list-project-usersList project user assignments• projectId: string - Project IDList of users assigned to project
list-project-tasksList project task assignments• projectId: string - Project IDList of tasks assigned to project
search-time-entriesSearches for time entries• from: string (optional) - Start date (YYYY-MM-DD)
• to: string (optional) - End date (YYYY-MM-DD)
• userId: string (optional) - User ID
• projectId: string (optional) - Project ID
• clientId: string (optional) - Client ID
List of time entries with details
get-time-entryGet time entry details• timeEntryId: string - Time Entry IDDetailed time entry information
create-time-entryCreate a new time entry• projectId: string - Project ID
• taskId: string - Task ID
• userId: string - User ID
• hours: number - Hours spent
• notes: string (optional) - Additional notes
Created time entry details

Note: More tools coming soon.

Usage

Claude Desktop

Open the Claude desktop config file claude-desktop-config.json and add the following under mcpServers:

{
  "mcpServers": {
    "Harvest": {
      "command": "npx",
      "args": [
        "-y",
        "@mayankg0324/mcp-server-harvest"
      ],
      "env": {
        "HARVEST_ACCOUNT_ID": "<Harvest Account ID>",
        "HARVEST_ACCESS_TOKEN": "<Harvest Personal Access Token>",
        "HARVEST_BASE_URL": "<Harvest Base URL>"
      }
    }
  }
}
Cursor IDE

Open the Cursor IDE config file ~/.cursor/mcp.json or <project-root>/.cursor/mcp.json and add the following under mcpServers:

{
  "mcpServers": {
    "Harvest": {
      "command": "npx",
      "args": [
        "-y",
        "@mayankg0324/mcp-server-harvest"
      ],
      "env": {
        "HARVEST_ACCOUNT_ID": "<Harvest Account ID>",
        "HARVEST_ACCESS_TOKEN": "<Harvest Personal Access Token>",
        "HARVEST_BASE_URL": "<Harvest Base URL>"
      }
    }
  }
}
Troubleshooting
spawn npx ENOENT or env: node: No such file or directory

This happens when your MCP client (Claude Desktop, Cursor) cannot find npx or node in its PATH. GUI applications often don't inherit your shell's PATH, especially if you use a version manager like nvm, fnm, or volta.

Fix: Use the full path to npx and include your Node bin directory in the PATH env variable:

# Find your npx and node paths
which npx
# e.g. /Users/you/.nvm/versions/node/v22.20.0/bin/npx

Then update your MCP config:

{
  "mcpServers": {
    "Harvest": {
      "command": "/Users/you/.nvm/versions/node/v22.20.0/bin/npx",
      "args": [
        "-y",
        "@mayankg0324/mcp-server-harvest"
      ],
      "env": {
        "PATH": "/Users/you/.nvm/versions/node/v22.20.0/bin:/usr/bin:/bin",
        "HARVEST_ACCOUNT_ID": "<Harvest Account ID>",
        "HARVEST_ACCESS_TOKEN": "<Harvest Personal Access Token>",
        "HARVEST_BASE_URL": "<Harvest Base URL>"
      }
    }
  }
}

Local Development

  1. Install dependencies:

    npm install
    
  2. Build the project:

    npm run build
    

    This will create a dist directory containing the compiled JavaScript files.

  3. To use the local development version, modify your MCP server config to point to the local build:

    {
      "mcpServers": {
        "Harvest": {
          "command": "node",
          "args": [
            "path/to/local/build/dist/index.js"
          ],
          "env": {
            "HARVEST_ACCOUNT_ID": "<Harvest Account ID>",
            "HARVEST_ACCESS_TOKEN": "<Harvest Personal Access Token>",
            "HARVEST_BASE_URL": "<Harvest Base URL>"
          }
        }
      }
    }
    
  4. Restart the client application (Claude, Cursor) to apply the changes.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.