Temporal vs io.github.theluckystrike/time-tracker
Temporal is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/time-tracker is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:24aeaca7c458 Forks (GitHub): 18 Pulls (Docker Hub): 41 218 Stars (Docker Hub): 2 Stars (GitHub): 60 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed, marked deprecated Version: 0.1.1 Forks (GitHub): 0 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 | Temporal | io.github.theluckystrike/time-tracker |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 60 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 41 218 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 18 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/temporal) | On your machine (https://github.com/theluckystrike/mcp-servers/releases/download/v0.1.1/time-tracker.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 29 | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gethosthewalrus/temporal-mcp | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Temporal
Manage Temporal workflows, schedules, namespaces, task queues, and workflow execution history from MCP clients.
io.github.theluckystrike/time-tracker
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
How to run each
Temporal As a local MCP server: Docker image
claude mcp add --env "TEMPORAL_API_KEY=<YOUR_TEMPORAL_API_KEY>" --transport stdio temporal -- docker run -i --rm -e TEMPORAL_API_KEY mcp/temporalRequires: TEMPORAL_API_KEY (secret)
io.github.theluckystrike/time-tracker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: MCP_LICENSE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.theluckystrike/time-tracker publish no list of tools, so we do not compare tools.
Settings each asks for
Only Temporal asks for
TEMPORAL_API_KEY (secret)TEMPORAL_HOSTTEMPORAL_NAMESPACETEMPORAL_TLS_CLIENT_CERT_PATHTEMPORAL_TLS_CLIENT_KEY_PATHTEMPORAL_TLS_ENABLED
Only io.github.theluckystrike/time-tracker asks for
MCP_LICENSE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Temporal · What it can do: io.github.theluckystrike/time-tracker · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.