Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Free RAM on Windows with the user's own Mem Reduct via its clean hotkey, without admin prompts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
MEMREDUCT_MCP_COOLDOWNYou need
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
claude mcp add memreduct --env MEMREDUCT_MCP_COOLDOWN=your-value -- npx -y memreduct-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"memreduct": {
"command": "npx",
"args": [
"-y",
"memreduct-mcp"
],
"env": {
"MEMREDUCT_MCP_COOLDOWN": "your-value"
}
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"memreduct": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"memreduct-mcp"
],
"env": {
"MEMREDUCT_MCP_COOLDOWN": "your-value"
}
}
}
}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.
MEMREDUCT_MCP_COOLDOWN envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account RepressedAlliance, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, MCPB on your computer.
In the same category: Context7, Codebase Memory, Exa
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
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
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.
Let AI agents (Claude Code, Codex, Cursor, Claude Desktop…) free RAM on Windows with your own [Mem Reduct](https://github.com/henrypp/memreduct), so a model, render or build that needs memory right now can get it, without admin prompts and without dialogs to click away.
中文说明
AI agents on Windows run long jobs on their own: builds, model inference, renders, many sessions and MCP servers side by side. Memory fills up along the way, and an agent has no way to give it back: idle sessions keep their pages resident, and trimming other programs' memory needs administrator rights the agent doesn't have. Mem Reduct can do it, but only when a person clicks it.
memreduct-mcp closes that gap: the Mem Reduct you already run cleans at the moments an agent needs it, and the agent is told what happened.
Mem Reduct already runs elevated in your tray. This server presses Mem Reduct's clean memory hotkey. Windows delivers registered hotkeys to the elevated Mem Reduct even from an unelevated agent, so no UAC prompt, scheduled task or admin service is involved. The server then waits until Mem Reduct records the clean (StatisticLastReduct in its ini) and measures available RAM before and after.
A hotkey clean shows no confirmation and no modal dialog. That is why this server does not use memreduct.exe -clean: the command line always ends with a message box that someone has to click.
This project does not include Mem Reduct. Mem Reduct is GPL-3.0 software by Henry++; this server only presses its hotkey.
Agents can't feel memory pressure, and written guidance alone isn't enough: in a 14-hour video job, an agent with this server's instructions never cleaned on its own, while the PC spent 75 minutes under 1 GB available. So in Claude Code the plugin also ships hooks, which run at each agent step:
| Moment | What happens |
|---|---|
| Before heavy work (subagents, workflows, background jobs, builds, renders), under 25% available | Cleans first. Measured gains fade within minutes under load, so this is the moment that counts. |
| A tool fails with an out-of-memory error (not GPU memory) | Cleans and tells the agent a retry is reasonable. |
| Under 15% for at least 30 seconds | Tells the agent the figures and the largest processes. Once per session, again after recovery or after 15 minutes. |
| Under 6% | Cleans at the next step. |
| Low again within 5 minutes of a clean | Doesn't clean again. Tells the agent the clean didn't hold, so it should lower parallelism, wait, or tell you. |
All sessions share one lock and cooldown. Hooks only run while an agent is working, so for the hours when none is, also set Mem Reduct's own *clean when usage is above* to about 92%.
Set MEMREDUCT_MCP_NEED_PCT, MEMREDUCT_MCP_WARN_PCT, MEMREDUCT_MCP_CRITICAL_PCT or MEMREDUCT_MCP_REARM_PCT to change the thresholds, and MEMREDUCT_MCP_HOOKS=off to turn the hooks off. What the hooks did is logged to %USERPROFILE%\.memreduct-mcp\hook-log.jsonl (memory figures, tool names and session ids only).
Other clients get the tools and the server's instructions, and no hooks yet, so whether the agent cleans on its own is up to the agent.
| Tool | What it does |
|---|---|
memory_status | Total, available and committed RAM, plus the largest processes. Read-only. |
clean_memory | Triggers a Mem Reduct clean and returns available RAM before and after, freedMB, and Mem Reduct's own figure when its result log is on. Optional needed_mb skips the clean when that much is already free. Has a cooldown (default 120 s, env MEMREDUCT_MCP_COOLDOWN). |
memreduct_setup_check | Says whether Mem Reduct is installed, running and has the hotkey enabled, and what to fix if not. |
clean_memory then also returns the amount Mem Reduct itself reports (memreductReported), so you don't have to trust the server's own measurement./plugin marketplace add RepressedAlliance/memreduct-mcp
/plugin install memreduct@memreduct-mcp
The server is on npm as memreduct-mcp:
codex mcp add memreduct -- npx -y memreduct-mcp
The server itself tells Codex when to clean. For the longer version Claude Code gets, also copy skills/memreduct/SKILL.md to %USERPROFILE%\.codex\skills\memreduct\SKILL.md (optional; new Codex sessions pick it up).
In clients configured with JSON (Cursor, Windsurf, Claude Desktop and others), add:
{
"mcpServers": { "memreduct": { "command": "npx", "args": ["-y", "memreduct-mcp"] } } }
Download memreduct-mcp.mcpb from Releases and open it, or drag it onto Claude Desktop's Settings > Extensions page. The cooldown can be changed in the extension's settings.
Clone the repository; dist/index.cjs is a self-contained bundle with no npm install needed. Use command node with argument C:\path\to\memreduct-mcp\dist\index.cjs.
Only at the right moment. Cleaning trims every program's working set and drops the standby cache, so available RAM jumps. How much depends on how much idle memory programs are holding. On a 16 GB test laptop, a process holding 6 GB of idle memory brought available RAM down to 3.6 GB; one clean_memory call brought it back to 10.9 GB (Mem Reduct's log: "Cleanup (Hotkey), 7.72 GB"). Right after a previous clean, with 10 GB already free, the same call freed under 1 GB.
Idle agent sessions are where it holds up best. With 8 long-lived Claude Code sessions (40 processes with their MCP servers) left idle after some work, one clean took their working set from 2.81 GB to 0.42 GB, and five minutes later they were at 1.02 GB. Their commit charge stayed at about 4 GB: cleaning frees physical RAM, it does not end processes or lower the commit charge.
Programs read those pages back from disk when they touch them again, so cleaning does not make a PC faster in general. It helps when a memory-hungry job is about to start and won't fit. The tool's cooldown and the bundled skill steer agents toward that use and away from cleaning on a schedule.
clean_memory then reports cleaned: false with a hint.npm install
npm run build # bundles src/ into dist/index.cjs npm test # end-to-end: starts the server and really cleans memory npm run test:policy # the hooks' decisions, without touching memory npm run pack:mcpb # builds memreduct-mcp.mcpb for Claude Desktop
MIT