Harvest Time Tracking MCP Server

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

Related MCP server: Harvest MCP Server

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

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