Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated yesterday
Install
Prompt Time
Overview
Description from the maker (original English)
Claude Desktop reminders for Windows. Survives MSIX boundary; persists across restarts. Zero deps.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account RyanJamesStewart, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Search & AI memoryi
- More stars than 0% of the other 5668 servers in this category
- Published to the registry more recently than 12% of the other 5668 servers in this category
- Basic checks equal to or better than 100% of the other 5668 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Prompt Time safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.2.6) reached the registry 6 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 21 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated 2 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
prompt-time
Schedule Windows desktop reminders directly from Claude Desktop. Zero dependencies — just PowerShell + Windows Task Scheduler.
What it does
Adds three tools to Claude Desktop:
| Tool | What it does |
|---|---|
schedule_reminder | Set a one-time or recurring desktop reminder |
list_reminders | Show every reminder currently scheduled |
cancel_reminder | Cancel a reminder by ID |
Reminders persist across reboots and Claude restarts. There is no cloud surface — everything runs locally.
Install in 60 seconds
- Download
prompt-time-v2.2.6.zipfrom the latest release. - Right-click the zip → Extract All. Windows must extract — running
install.batfrom inside the zip preview window will not work. - Open the extracted folder, double-click `install.bat`.
- If Claude Desktop is running, the installer will prompt to restart it. Accept — the MCP tools only show up after Claude Desktop is restarted.
- Done. The tools are live.
No Node, no npm, no admin rights, no internet required.
The extracted folder is disposable after install. v2.2.6+ copies both the MCP server and the watcher into the prompt-time data directory at install time, and points Claude Desktop's config + the scheduled task at the data-dir copies. You can move or delete the extracted folder afterwards without breaking anything. (Re-run
install.batfrom a fresh extract if you ever want to upgrade.)
Usage examples
Just talk to Claude:
"Remind me to send the weekly update at 4pm today"
"Set a reminder every weekday at 9am to check my inbox"
"Remind me about the board call next Monday at 2pm"
"What reminders do I have set?"
"Cancel reminder PROMPTTIME-A1B2C3D4"
Recurrence: once, daily, weekly, weekdays. Granularity is ~10 seconds (the watcher's poll interval).
How it works
Two pieces:
- MCP server (
prompt_time.ps1) — runs inside Claude Desktop's process tree. Validates and enqueues reminders to a JSONL file on disk. - Watcher daemon (
prompt-time-watcher.ps1) — registered once at install as a Task SchedulerAt LogOntask. Polls the queue, renders the toast popup in-process, and advances recurring entries.
The MCP server never talks to Task Scheduler at runtime, never spawns a process, and never displays UI. It only writes one JSONL line per reminder. Everything else is the watcher's job.
Why two processes — the MSIX boundary
Claude Desktop ships as an MSIX-packaged app. MSIX containers transparently virtualize file writes: a server running inside the package that calls Add-Content $env:APPDATA\prompt-time\queue.jsonl does not write to %APPDATA%\Roaming\prompt-time\queue.jsonl — it writes to a per-package shadow tree under %LOCALAPPDATA%\Packages\ \LocalCache\….
Anything Task Scheduler spawns runs *outside* the package, so a per-reminder schtasks task would look for files at the real path and find nothing.
prompt-time resolves this once: at startup, every component (prompt_time.ps1, prompt-time-watcher.ps1, install.ps1, uninstall.ps1) discovers the Claude AppX package and computes the same canonical data directory inside its LocalCache. Server writes and watcher reads land at the same physical file. The watcher renders the popup itself rather than asking Task Scheduler to do it, which keeps every state-bearing operation on the same side of the boundary.
The installer also pre-creates the queue file at the canonical path before the MCP server's first write — without that, MSIX file-virtualization redirects new file creation into the package shadow even though existing files at the real path are written through.
The same trap bites the Claude Desktop config itself. If MSIX-packaged Claude has ever written to its own claude_desktop_config.json (e.g. saving preferences), MSIX materializes a per-package shadow copy at %LOCALAPPDATA%\Packages\ \LocalCache\Roaming\Claude\claude_desktop_config.json and then *reads from the shadow* on every subsequent boot. An installer that writes only to %APPDATA% becomes invisible to Claude on those machines. v2.2.3+ reads shadow-first as the source of truth and writes the merged config to both paths atomically; uninstall removes from both. v2.2.4 adds post-write self-verify so install fails loudly with an actionable error if the entry doesn't survive (AV rollback, managed-policy override, etc.) instead of reporting a false success. Run diagnose.bat for a full breakdown.
Troubleshooting
Notifications muted by Focus Assist. Windows Focus Assist (Settings → System → Focus) silences toasts. Either turn it off or add powershell.exe to the Priority list.
Tools don't appear in Claude Desktop.
- Fully quit Claude Desktop (right-click tray icon → Quit) and reopen it. The "X" close button only minimizes; tools won't reload.
- Run `diagnose.bat` from the extracted folder. It reads your config, spawns
prompt_time.ps1the way Claude Desktop will, reads Claude Desktop's MCP logs, and prints an actionable hint for each failure. Most "install ran but nothing appeared" cases are diagnosed here without needing IT. - If
diagnose.batsays all checks pass but tools still don't show: rundiagnose.bat -Jsonand attach the output when filing a bug.
`install.bat` closes immediately. Run it from a cmd prompt instead so you can read the error: install.bat from inside the unzipped folder. The installer also writes a debug log at %APPDATA%\prompt-time\prompt-time.debug.log (or the MSIX LocalCache equivalent) — check there.
Reminders not firing. Check the watcher task is running:
Get-ScheduledTask -TaskName PROMPTTIME-Watcher | Get-ScheduledTaskInfoLastTaskResult should be 267009 (running) or 0 (success).
Uninstall
Double-click `uninstall.bat`. It removes the prompt-time entry from Claude Desktop's config, deletes the PROMPTTIME-Watcher scheduled task, and clears the data directory. Other MCP servers in your config are untouched.
Tests
.\tests\run.ps1Installs Pester 5 if missing, runs the Pester suite, and emits NUnit XML at tests/pester-results.xml. CI runs the same harness plus Invoke-ScriptAnalyzer on every push.
Security
See SECURITY.md for the trust model, supply-chain story, and how to report a vulnerability. Short version: the trust boundary is your local Windows user; reminder titles and messages are stored on disk in cleartext (don't put secrets in them); prompt-time registers a logon-time scheduled task as a standard persistence primitive.
License
MIT — see LICENSE.
Built by Ryan Stewart