macos-say vs Dates-LE
macos-say is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
macos-say is a plugin bundle for AI coding tools published by gabrielkoerich. No marketplace we read lists it any more. Dates-LE is an MCP server published by nolindnaidoo. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |   Dates-LE | |
|---|---|---|
| Community marketplace gabrielkoerich/skills | Removed on 2026-10-21 Version: not stated Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.5.0 Downloads/month (npm): 1 597 Downloads/week (npm): 130 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.6.1 Downloads/month (npm): 1 597 Downloads/week (npm): 130 Forks (GitHub): 0 Stars (GitHub): 1 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 | macos-sayno longer listed · | Dates-LE |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 6 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (dates-le-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/gabrielkoerich/skills | github.com/nolindnaidoo/dates-le |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 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 macos-say
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Reads text aloud locally on Windows, macOS, and Linux. No API key, account, or cloud service.
-
This skill converts text to high-quality audio files using ElevenLabs API. Use this skill when users request text-to-spe
-
Turn text into natural-sounding MP3 voice-overs in 6 languages. Free plan included.
-
Text to natural speech as MP3: 38 voices, 7 languages, 1,000 chars per call. Paid per call, x402.
-
Make audiobooks locally with Kokoro voices from your AI assistant. Nothing leaves your computer.
-
Add Grok voice to an app: realtime speech-to-speech, speech-to-text dictation, text-to-speech read-aloud, and a log-driven fix loop for voice sessions.
What each says it does
macos-say
Free offline text-to-speech on macOS with the built-in `say` command. Speak text aloud, narrate a file, or render speech to wav/m4a/aiff using system voices. No API key, no network, no cost. Use when asked to speak, read aloud, narrate, voice, or generate TTS audio.
Dates-LE
Extract dates and timestamps from logs, data files and code, with their format and position.
How to run each
macos-say
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Dates-LE As a local MCP server: npm package
claude mcp add --transport stdio dates-le -- npx -y dates-le-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: macos-say · What it can do: Dates-LE · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.