A
licenseA
qualityC
maintenanceMCP server for Harvest time tracking, enabling users to manage timers, log time, and generate reports through natural language.
11
1
MIT
harvest-forecast-mcp
by AZX-PBC-OSS
Related Servers
Alternatives to harvest-forecast-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server for Harvest time tracking. Manage time entries, start/stop timers, handle projects, clients, tasks, and generate time and expense reports via the Harvest API v2.54248MIT
- AlicenseAqualityAmaintenanceAn MCP server that provides AI assistants with access to the EARLY time tracking public API, enabling time entry management, activity management, and report generation through natural language.1422MIT
- AlicenseAqualityBmaintenanceAn MCP server for the Paymo time-tracking API, enabling AI clients to read and write tasks, time entries, projects, and more via natural language.126MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to interact with Clockify time tracking via curated workflows and a generic API tool for managing workspaces, projects, tasks, and time entries.15MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides MCP integration for Harvest's time tracking, project management, and invoicing functionality, enabling natural language interaction with Harvest API through tools for managing clients, time entries, projects, tasks, and users.-
TDQS
A3.6/5.0
Scored across 34 tools
Disambiguation5/5
Each tool targets a distinct resource or action, with clear separation between Forecast and Harvest operations. Overlaps like person_schedule vs get_person_heatmap are differentiated by purpose (combined view vs scheduling heatmap). No tools are redundant or confusing.
Naming Consistency5/5
Tools predominantly follow a consistent verb_noun pattern (e.g., create_assignment, list_forecast_people). Exceptions like all_projects_schedule and who_is_available are still descriptive and follow a logical naming scheme. No mixed casing or erratic patterns.
Tool Count4/5
With 34 tools, the set is comprehensive but slightly above average. However, given the dual-API coverage (Harvest and Forecast) and the inclusion of cross-reference tools, the count is justified and not excessive. Each tool serves a clear purpose.
Completeness4/5
The tool surface covers core CRUD for assignments and time entry creation, plus comprehensive listing and cross-referencing. Minor gaps exist (no time entry update/delete, no Harvest project creation), but these are likely out of scope for a scheduling/time-tracking integration server.
Maintenance
ActivitySlowing
ResponsivenessNo issues