Temporal vs Shiftyasan Shift Scheduling
Temporal is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). Shiftyasan Shift Scheduling is an MCP server published by shiftyasan.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  Temporal |  Shiftyasan Shift Scheduling |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:24aeaca7c458 Forks (GitHub): 20 Pulls (Docker Hub): 41 356 Stars (Docker Hub): 2 Stars (GitHub): 60 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 168 Downloads/week (npm): 31 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
| Fact | Temporal | Shiftyasan Shift Scheduling |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 60 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 41 356 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 20 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/temporal) | Remote server (api.shiftyasan.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 29 | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gethosthewalrus/temporal-mcp | github.com/shiftyasan/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 41 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
Temporal
Manage Temporal workflows, schedules, namespaces, task queues, and workflow execution history from MCP clients.
Shiftyasan Shift Scheduling
Generate optimized work shift schedules from staffing demand, availability and fairness rules.
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)
Shiftyasan Shift Scheduling As a remote MCP server
claude mcp add --transport http shiftyasan-shift-scheduling https://api.shiftyasan.com/mcpRequires: SHIFTYASAN_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Shiftyasan Shift Scheduling has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Shiftyasan Shift Scheduling 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 Shiftyasan Shift Scheduling asks for
SHIFTYASAN_API_KEY (secret)SHIFTYASAN_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Temporal · What it can do: Shiftyasan Shift Scheduling · 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.