Atimelogger MCP vs Timebook Cli — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Atimelogger MCP vs Timebook Cli
In-depth architectural comparison of the Atimelogger MCP and Timebook Cli 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
Timebook Cli
Workplace & Productivity · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Atimelogger MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Timebook Cli 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)
Official MCP server for Timebook — time tracking, invoicing, and bookkeeping for freelancers and solo LLCs. Manage clients and projects, start/stop timers, and log, update, and delete time entries. Runs locally via the @squidcode/timebook npm CLI or as a hosted OAuth endpoint at https://usetimebook.com/mcp. Published in the MCP registry as io.github.squidcode/timebook.
Category & Scope
Tools & Capabilities Breakdown
Atimelogger MCP Tools (10)
get_current_status
Running/paused activities with elapsed time
list_activity_types
Activity type names as a group tree (source of names for other tools)
start_activity
Start by type name; optional backdating (`at` wall-clock time or `started_minutes_ago`)
stop_activity
Stop the active activity (name optional if only one is active); same backdating options
pause_resume_activity
Pause or resume
log_interval
Retroactively log a completed entry (wall-clock times, optional comment/tags)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Atimelogger MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Timebook Cli belongs to Workplace & Productivity using local stdio subprocess. Select Atimelogger MCP when you need capabilities focused on workplace & productivity and Timebook Cli 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
Timebook Cli Tools (10)
whoami
Current authenticated user (read-only)
list_projects
All projects in scope (read-only)
list_clients
All clients in scope (read-only)
get_active_timer
The running timer, or `null` (read-only)
start_timer
Start a timer on a project
stop_timer
Stop the running timer
log_time
Log a manual entry (`duration` OR `startTime`+`endTime`)
list_entries
Recent entries (default 50, max 500), project + date filters
update_entry
Edit one or more fields on an entry (description, duration, startTime, endTime, project, rate). Token must own the entry.
delete_entry
Delete an entry. Token must own it. Invoiced entries are locked.