Harvest MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HARVEST_ACCOUNT_ID | Yes | Your Harvest account ID | |
| HARVEST_ACCESS_TOKEN | Yes | Your Harvest API access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| harvest_list_time_entriesB | List time entries with optional filters. Use about {"tool": "harvest_list_time_entries"} for detailed usage examples. |
| harvest_create_time_entryC | Create a new time entry. Use about {"tool": "harvest_create_time_entry"} for detailed parameters and examples. |
| harvest_update_time_entryC | Update an existing time entry. Use about {"tool": "harvest_update_time_entry"} for detailed parameters and examples. |
| harvest_delete_time_entryC | Delete a time entry. Use about {"tool": "harvest_delete_time_entry"} for detailed usage and warnings. |
| harvest_restart_timerC | Restart a stopped time entry timer. Use about {"tool": "harvest_restart_timer"} for detailed workflow and examples. |
| harvest_stop_timerC | Stop a running time entry timer. Use about {"tool": "harvest_stop_timer"} for detailed workflow and examples. |
| aboutA | Get detailed information about the Harvest MCP server and its tools. Call about without parameters for general info, or with {"tool": "tool_name"} for specific tool documentation. |
| versionA | Get version information about the Harvest MCP server. |
| harvest_list_projectsC | List all projects with filtering options. Use about {"tool": "harvest_list_projects"} for detailed parameters and examples. |
| harvest_get_projectC | Get details of a specific project. Use about {"tool": "harvest_get_project"} for detailed usage examples. |
| harvest_list_tasksC | List all tasks with filtering options. Use about {"tool": "harvest_list_tasks"} for detailed parameters and examples. |
| harvest_get_current_userB | Get information about the authenticated user. Use about {"tool": "harvest_get_current_user"} for detailed response format. |
| harvest_list_usersC | List all users in the account with filtering. Use about {"tool": "harvest_list_users"} for detailed parameters and examples. |
| harvest_list_clientsC | List all clients with filtering options. Use about {"tool": "harvest_list_clients"} for detailed parameters and examples. |
| harvest_time_reportC | Generate detailed time reports for date ranges. Use about {"tool": "harvest_time_report"} for filtering options and examples. |
| harvest_list_project_assignmentsC | List project assignments for the current user. Use about {"tool": "harvest_list_project_assignments"} for detailed usage. |
| harvest_list_task_assignmentsC | List task assignments for a project. Use about {"tool": "harvest_list_task_assignments"} for detailed workflow and examples. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Every tool has a clearly distinct purpose targeting specific Harvest API resources and actions. The naming convention makes it immediately clear which resource (clients, projects, tasks, time entries, users) and which operation (list, get, create, update, delete, restart, stop, report) each tool performs. There is no ambiguity or overlap between tools.
All tools follow a perfectly consistent 'harvest_verb_noun' pattern (e.g., harvest_list_clients, harvest_create_time_entry). The two exceptions (about and version) are clearly meta-tools for server information and maintain readability. The naming convention is predictable and systematic throughout the toolset.
With 17 tools, this server provides comprehensive coverage of Harvest's core time-tracking and project management functionality. Each tool serves a specific, necessary purpose in the domain (client/project/task/user management, time entry lifecycle, reporting). The count is well-scoped for the complexity of the Harvest API without being overwhelming.
The toolset provides complete CRUD/lifecycle coverage for time entries (create, list, update, delete, restart/stop timers, generate reports) and comprehensive read/list operations for all core resources (clients, projects, tasks, users, project/task assignments). There are no obvious gaps for time-tracking workflows, and the about/version tools provide necessary meta-information.