work-session-tools vs Cronfy
work-session-tools is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
work-session-tools is a plugin bundle for AI coding tools published by Alex Kopylov. No marketplace we read lists it any more. Cronfy is an MCP server published by AndreyBroker. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-06. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Cronfy | |
|---|---|---|
| Community marketplace alex-kopylov/zweihander | Removed on 2026-10-24 Version: 0.6.6 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 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
| Fact | work-session-toolsno longer listed · | Cronfy |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (cronfy-app.web.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/alex-kopylov/zweihander | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-20 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of work-session-tools
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Track tasks, finalize sessions, resume context — all through natural language.
-
A customized version of Anthropic's productivity plugin with two additions: the update skill reads transcripts across all chats in the project (not just the current one), and each…
-
A plugin to turn Claude Code into your personal assistant
-
Interactive skill that analyzes a task, proposes an agent team composition with roles and responsibilities, and creates the team after user confirmation
-
Shared task wall, memory, reports, channels and Dashboard for Claude Code and Codex; Claude Code plugin installation and an independent Codex adapter
-
Manage tasks, plan your day, and build up memory of important context about your work. Syncs with your calendar, email, and chat to keep everything organized and on track.
What each says it does
work-session-tools
Productivity, orchestration, and handoffs within an assistant session.
Cronfy
Time tracking you talk to: log, check and fix your work hours from your AI assistant.
How to run each
work-session-tools
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Cronfy As a remote MCP server
claude mcp add --transport http cronfy https://cronfy-app.web.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Cronfy has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: work-session-tools · What it can do: Cronfy · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.