Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Free RAM on Windows with the user's own Mem Reduct via its clean hotkey, without admin prompts.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
MEMREDUCT_MCP_COOLDOWN필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
링크는 제작자의 파일로 바로 연결돼요. 우리가 보관하거나 다시 패키징하지 않아요. 파일을 열면 Claude Desktop이 설치해요.
터미널에서 이 명령어를 실행하세요
claude mcp add memreduct --env MEMREDUCT_MCP_COOLDOWN=your-value -- npx -y memreduct-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"memreduct": {
"command": "npx",
"args": [
"-y",
"memreduct-mcp"
],
"env": {
"MEMREDUCT_MCP_COOLDOWN": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"memreduct": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"memreduct-mcp"
],
"env": {
"MEMREDUCT_MCP_COOLDOWN": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
MEMREDUCT_MCP_COOLDOWN env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 RepressedAlliance 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.1)은 4일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js, MCPB도 있어야 해요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
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.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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