Persistent memory for AI agents — local JSON, zero config, no server required.
AI agents forget everything between sessions. gives them persistent memory — local, portable, and works with any agent. Every dev using AI professionally hits this wall: Existing solutions (Mem0, Zep, Letta) require servers, API keys, and cloud accounts. You just want the agent to remember your project. Zero friction. No CLI commands. Native IDE integration. 1. Add to your IDE's MCP config: The…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
AI agents forget everything between sessions. gives them persistent memory — local, portable, and works with any agent. Every dev using AI professionally hits this wall: Existing solutions (Mem0, Zep, Letta) require servers, API keys, and cloud accounts. You just want the agent to remember your project. Zero friction. No CLI commands. Native IDE integration. 1. Add to your IDE's MCP config: The agent now automatically reads memory at session start, writes when learning something new, and…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.