Ext Ops Panel
Open dashboard
Comparison

Temporal vs Timesheet

Temporal is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-10-15. 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

Where each is published
MarketplaceTemporalTimesheet
Docker MCP Catalog Listed
Version: sha256:24aeaca7c458
Forks (GitHub): 19
Pulls (Docker Hub): 41 299
Stars (Docker Hub): 2
Stars (GitHub): 60
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.2
Downloads/month (npm): 821
Downloads/week (npm): 59
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

Temporal vs Timesheet
FactTemporalTimesheet
Marketplaces that list it11
Stars (GitHub) (differs)60 (better)1 (worse)
Pulls (Docker Hub) (differs)41 299No figure on Docker Hub
Forks (GitHub) (differs)19 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/temporal)Remote server (mcp.timesheet.io)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)29Not published
Environment variables it asks for (differs)6, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/gethosthewalrus/temporal-mcpgithub.com/timesheetio/timesheet-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

Temporal

In its own words, on Docker MCP Catalog:

Manage Temporal workflows, schedules, namespaces, task queues, and workflow execution history from MCP clients.

Timesheet

In its own words, on Official MCP Registry:

timesheet.io MCP server - manage timers, projects, tasks and reports

How to run each

Temporal As a local MCP server: Docker image

Claude Code
claude mcp add --env "TEMPORAL_API_KEY=<YOUR_TEMPORAL_API_KEY>" --transport stdio temporal -- docker run -i --rm -e TEMPORAL_API_KEY mcp/temporal

Requires: TEMPORAL_API_KEY (secret)

Timesheet As a remote MCP server

Claude Code
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

The marketplaces of Timesheet publish no list of tools, so we do not compare tools.

Settings each asks for

Only Temporal asks for

  • TEMPORAL_API_KEY (secret)
  • TEMPORAL_HOST
  • TEMPORAL_NAMESPACE
  • TEMPORAL_TLS_CLIENT_CERT_PATH
  • TEMPORAL_TLS_CLIENT_KEY_PATH
  • TEMPORAL_TLS_ENABLED

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: Temporal · What it can do: Timesheet · 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.

Where the data comes from: how the catalog is built