session-clock vs Literature Clock
session-clock is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
session-clock is a plugin bundle for AI coding tools published by baselane-sh. No marketplace we read lists it any more. Literature Clock is an MCP server published by markusvankempen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |   Literature Clock | |
|---|---|---|
| Community marketplace baselane-sh/mods-catalog | Removed on 2026-10-22 Version: 0.5.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.2 Downloads/month (npm): 806 Downloads/week (npm): 26 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 | session-clockno longer listed · | Literature Clock |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (literature-clock-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/baselane-sh/mods | github.com/markusvankempen/literature-clock-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
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 session-clock
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Mod: band above the prompt with turn, speed, cost, prompt cache countdown and context; notifies before the cache expires.
-
Your plan's 5-hour and 7-day usage as small bars above the prompt, with the reset countdown and the session's cost.
-
Shareable timer links for countdowns, clock times, Pomodoro, Tabata and step recipes. No account.
-
Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.
-
A lightweight plugin that estimates task duration, automatically opens a timer, and reminds you to step away while Claude works. Reduce passive screen time during AI-assisted…
-
Personal time tracker: start timers, log time and summarize your hours by activity.
What each says it does
session-clock
A band above the prompt with the wall clock and how long the session has run (14:05 · 1h 12m).
Literature Clock
A line for the current minute, from literature, copyright-free books, or an original voice.
How to run each
session-clock
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Literature Clock As a local MCP server: npm package
claude mcp add --env "ADMIN_PASSWORD=<YOUR_ADMIN_PASSWORD>" --env "MCP_API_KEY=<YOUR_MCP_API_KEY>" --transport stdio literature-clock-mcp -- npx -y literature-clock-mcpRequires: ADMIN_PASSWORD (secret), MCP_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of session-clock publish no settings it asks for, so we do not compare settings.
What it can do: session-clock · What it can do: Literature Clock · 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.