Ext Ops Panel
Open dashboard
Comparison

Temporal vs Shiftly Staff Scheduling Demo

Temporal is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). Shiftly Staff Scheduling Demo is an MCP server published by easyshiftplan.zhiyong.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceTemporalShiftly Staff Scheduling Demo
Docker MCP Catalog Listed
Version: sha256:24aeaca7c458
Forks (GitHub): 20
Pulls (Docker Hub): 41 445
Stars (Docker Hub): 2
Stars (GitHub): 60
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.8
No figure published
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 Shiftly Staff Scheduling Demo
FactTemporalShiftly Staff Scheduling Demo
Marketplaces that list it11
Stars (GitHub) (differs)60No figure on GitHub
Pulls (Docker Hub) (differs)41 445No figure on Docker Hub
Forks (GitHub) (differs)20No figure on GitHub
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/temporal)Remote server (easyshiftplan.zhiyong.dev/mcp/demo)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)29Not 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-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 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

In its own words, on Docker MCP Catalog:

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

Shiftly Staff Scheduling Demo

In its own words, on Official MCP Registry:

No-login MCP demo for isolated fictional staff schedules; drafts are never saved or published.

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)

Shiftly Staff Scheduling Demo As a remote MCP server

Claude Code
claude mcp add --transport http shiftly-scheduling https://easyshiftplan.zhiyong.dev/mcp/demo

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

Only Shiftly Staff Scheduling Demo has a remote endpoint we check. How we check endpoints

Tools each declares

Only Temporal has

  • batch_cancel
  • batch_cancel_activities
  • batch_signal
  • batch_terminate
  • batch_terminate_activities
  • cancel_activity
  • cancel_workflow
  • continue_as_new
  • count_activities
  • create_schedule
  • delete_schedule
  • describe_activity
Show the remaining 17
  • describe_workflow
  • execute_activity
  • get_activity_result
  • get_workflow_history
  • get_workflow_result
  • list_activities
  • list_schedules
  • list_workflows
  • pause_schedule
  • query_workflow
  • signal_workflow
  • start_activity
  • start_workflow
  • terminate_activity
  • terminate_workflow
  • trigger_schedule
  • unpause_schedule

Only Shiftly Staff Scheduling Demo has

  • get_demo_feedback_reply
  • get_public_product_info
  • prepare_share_draft
  • run_public_demo
  • submit_demo_feedback

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Shiftly Staff Scheduling Demo as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Shiftly Staff Scheduling Demo publish no settings it asks for, so we do not compare settings.

What it can do: Temporal · What it can do: Shiftly Staff Scheduling Demo · 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