In-depth architectural comparison of the Inbox Zero and Time tracker 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
Inbox Zero
Workplace & Productivity · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Time tracker
Workplace & Productivity · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Inbox Zero if you need specialized Workplace & Productivity tools running via a local process. Choose Time tracker 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 Inbox Zero when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Primary tools included: Finds emails requiring replies, Finds emails requiring follow-up, Connects Inbox Zero functionality to Gmail.
Start a timer on a project (optional task, tags, rate, currency). Starting a new one stops and logs the old one. A partial project name that matches exactly one existing project is used as that project.
timer_stop
Stop the running timer, write the entry, return the duration.
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).
Inbox Zero is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Time tracker belongs to Workplace & Productivity using local stdio subprocess. Select Inbox Zero when you need capabilities focused on workplace & productivity and Time tracker when you require tools for workplace & productivity.
Log time you already worked (start plus end or minutes), with an optional rate and currency: rate "90 euros an hour" bills as EUR 225.00 for 2.5 h. Partial project names resolve like `timer_start`.
entry_list
Compact table of entries, filtered by date range and project.
entry_edit
Change any field of an entry.
entry_delete
Delete an entry by id.
project_set_rate
Set the hourly rate and currency used for money totals (currency accepts codes or words: EUR, euros, pounds, zl). `apply_to_existing: true` re-rates time already logged for that project; add `only_missing: true` to touch only entries that carry no rate.
report
Hours and money for a period, optionally grouped by project, day, task or tag; omit `group_by` for the plain total per currency. Table, JSON or CSV. Hours already invoiced are left out; pass `unbilled_only: false` for the full timesheet.
export_csv
Write entries to a CSV file and return the path.
invoice_summary
Invoice-ready line items for one project: hours, rate, amount, total, in the currency the time was logged in. One line per task and rate, so no line ever shows a blended rate nobody agreed. Returns the `entry_ids` behind the lines, and skips hours already invoiced (`unbilled_only: false` includes t…
entry_mark_billed
Stamp the hours that went on an invoice with its number (`ids` from `invoice_summary`, or `project` + `from` + `to`), so `report` and `invoice_summary` stop offering them and the same hours are never billed twice.