Model Context Protocol server for Harvest API v2
Harvest MCP server exists for a simple reason — assistants are far more useful when they can act on Harvest directly instead of describing what you should do. Model Context Protocol server for Harvest API v2.
The server ships on npm as @ianaleck/harvest-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Harvest is connected, these are the calls the assistant has available:
get_company — Get company information and settingslist_time_entries — List time entries with filteringget_time_entry — Get specific time entry detailscreate_time_entry — Create new time entryupdate_time_entry — Update existing time entrydelete_time_entry — Delete time entrystart_timer — Start a timer for a taskstop_timer — Stop running timerrestart_timer — Restart a previous time entrylist_projects — List all projects with filteringget_project — Get specific project detailscreate_project — Create new projectYou will need 2 environment variables: HARVEST_ACCESS_TOKEN, HARVEST_ACCOUNT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Harvest's toolset — get_company, list_time_entries, get_time_entry and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ianaleck; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Harvest's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_company | Get company information and settings |
| list_time_entries | List time entries with filtering |
| get_time_entry | Get specific time entry details |
| create_time_entry | Create new time entry |
| update_time_entry | Update existing time entry |
| delete_time_entry | Delete time entry |
| start_timer | Start a timer for a task |
| stop_timer | Stop running timer |
| restart_timer | Restart a previous time entry |
| list_projects | List all projects with filtering |
| get_project | Get specific project details |
| create_project | Create new project |
| update_project | Update project details |
| delete_project | Delete project |
{
"mcpServers": {
"harvest-1": {
"command": "npx",
"args": ["-y", "@ianaleck/harvest-mcp-server"],
"env": {
"HARVEST_ACCESS_TOKEN": "your-value",
"HARVEST_ACCOUNT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| HARVEST_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| HARVEST_ACCOUNT_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.