Time Doctor vs Timesheet
Time Doctor is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). Timesheet is an MCP server published by timesheetIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.0.2 Downloads/month (npm): 766 Downloads/week (npm): 33 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Time Doctor | Timesheet |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/wyre-ai/timedoctor-mcp:v1.0.3) | Remote server (mcp.timesheet.io) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/wyre-ai/timedoctor-mcp | github.com/timesheetio/timesheet-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-03 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 21 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Time Doctor
MCP server for Time Doctor's employee time-tracking API — companies, users, projects, and stats.
Timesheet
timesheet.io MCP server - manage timers, projects, tasks and reports
How to run each
Time Doctor As a local MCP server: Docker image
claude mcp add --env "TIMEDOCTOR_EMAIL=<YOUR_TIMEDOCTOR_EMAIL>" --env "TIMEDOCTOR_PASSWORD=<YOUR_TIMEDOCTOR_PASSWORD>" --transport stdio timedoctor-mcp -- docker run -i --rm -e TIMEDOCTOR_EMAIL -e TIMEDOCTOR_PASSWORD ghcr.io/wyre-ai/timedoctor-mcp:v1.0.3
Requires: TIMEDOCTOR_EMAIL, TIMEDOCTOR_PASSWORD (secret)
Timesheet As a remote MCP server
claude mcp add --transport http timesheet-mcp https://mcp.timesheet.io
Requires: TIMESHEET_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Timesheet has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Time Doctor asks for
AUTH_MODELOG_LEVELMCP_TRANSPORTTIMEDOCTOR_EMAILTIMEDOCTOR_PASSWORD (secret)
Only Timesheet asks for
TIMESHEET_API_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Time Doctor · What it can do: Timesheet · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.