In-depth architectural comparison of the Atimelogger MCP and Harvest MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Atimelogger MCP
Workplace & Productivity · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Harvest MCP Server
Workplace & Productivity · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose Atimelogger MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Harvest MCP Server if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Atimelogger MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP server exposing the ATimeLogger REST API (activities, reports, types)
Harvest time tracking integration with 40+ tools for managing time entries, projects, clients, tasks, and generating time reports via the Harvest API v2
Atimelogger MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Harvest MCP Server belongs to Workplace & Productivity using local stdio subprocess. Select Atimelogger MCP when you need capabilities focused on workplace & productivity and Harvest MCP Server when you require tools for workplace & productivity.
Change the comment/tags of an existing entry (running or past) without touching its times
time_report
Aggregated per-type statistics for a period (`today`, `this_week`, `last_month`, … or explicit dates)
list_intervals
Raw history grouped by day, paged, max 100-day range
app_help
Official app documentation ([atimelogger.pro/docs](https://atimelogger.pro/docs/)) — the assistant looks up how app features work (goals, widgets, sync, export, …) instead of guessing