Ext Ops Panel
Open dashboard
Comparison

Temporal vs TopTimesheets Deskless Clock-In & Payroll ROI

Temporal is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). TopTimesheets Deskless Clock-In & Payroll ROI is an MCP server published by toptimesheets.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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
MarketplaceTemporalTopTimesheets Deskless Clock-In & Payroll ROI
Docker MCP Catalog Listed
Version: sha256:8d5df30a1c6c
Forks (GitHub): 19
Pulls (Docker Hub): 42 632
Stars (Docker Hub): 2
Stars (GitHub): 66
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 1.12.0
Downloads/month (PyPI): 5 561
Downloads/week (PyPI): 2 872
Forks (GitHub): 19
Stars (GitHub): 66
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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 TopTimesheets Deskless Clock-In & Payroll ROI
FactTemporalTopTimesheets Deskless Clock-In & Payroll ROI
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)66 (better)0 (worse)
Pulls (Docker Hub) (differs)42 632No figure on Docker Hub
Forks (GitHub) (differs)19 (better)0 (worse)
Last release (differs)2026-11-02Not published
Where it runs (differs)On your machine (mcp/temporal)Not stated
Transport (differs)stdioNot stated
Tools it declares (differs)31Not published
Environment variables it asks for (differs)6, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/gethosthewalrus/temporal-mcpgithub.com/mewebecom/mewebe-mcp-servers
Changes in the last 7 days (differs)62
First seen (differs)2026-10-112026-11-10

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.

TopTimesheets Deskless Clock-In & Payroll ROI

In its own words, on Official MCP Registry:

WhatsApp, mobile, and kiosk GPS selfie clock-ins with instant payroll export for deskless teams.

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)

TopTimesheets Deskless Clock-In & Payroll ROI

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of TopTimesheets Deskless Clock-In & Payroll ROI publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of TopTimesheets Deskless Clock-In & Payroll ROI publish no settings it asks for, so we do not compare settings.

What it can do: Temporal · What it can do: TopTimesheets Deskless Clock-In & Payroll ROI · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). 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