Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
claude mcp add io.github.420247jake-session-forge -- npx -y session-forge@2.0.3In einem Terminal ausführen.
{ "mcpServers": { "io.github.420247jake-session-forge": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Never start from zero. Persistent session intelligence for AI coding assistants.
Session-forge gives your AI coding assistant memory that survives across sessions. It tracks decisions, dead ends, user preferences, and session state — so every conversation builds on the last one instead of starting from scratch.
Works with Claude Code, Cursor, , and any MCP-compatible client.
Persistent memory and session intelligence for AI coding assistants. Zero config.
claude mcp add session-forge -- npx session-forge
Add to your MCP settings:
{
"mcpServers": {
"session-forge": {
"command": "npx",
"args": ["-y", "session-forge"]
}
}
}
That's it. No database, no Docker, no config files.
data_manage actions:
stats — entry counts and schema versions for all storesexport — dump all data as JSONprune — remove entries older than N days (default: 90)clear — wipe a specific store (journal, decisions, dead_ends, profile, or all)data_list + data_delete workflow:
data_list with store="decisions" — see numbered list of all decisionsdata_list with store="decisions", query="minecraft" — filter by keyworddata_delete with store="decisions", entry_index=3 — remove entry #3 from the listAll data is stored locally as plain JSON files:
Override with the SESSION_FORGE_DIR environment variable:
SESSION_FORGE_DIR=/custom/path npx session-forge
Files:
~/.session-forge/
profile.json # User preferences and projects
journal.json # Session summaries (last 100)
decisions.json # Decision log (last 200)
dead-ends.json # Failed approaches (last 100)
sessions/
active.json # Current checkpoint
history/ # Archived sessions
Data files include a schema_version field for future migration support.
Add this to your project's CLAUDE.md to teach the AI when to call each tool:
## Session Flow
### Fresh session
1. Call `full_context_recall` — get profile, journals, decisions, dead ends
2. Call `session_restore` — check for interrupted work
### During work
- `decision_record` — when making a significant architectural choice
- `dead_end_record` — when something fails and we learn why
- `session_checkpoint` — every 10-15 tool calls during long sessions
### Session end
1. Call `journal_entry` — record what happened
2. Call `session_complete` — archive the checkpoint
related_dead_ends and led_to_decision fieldsfull_context_recall can read your MEMORY.md and suggest decisions/dead ends that should be saved to memoryerrors_encountered, key_findings, decisions_made, dead_ends_hitlinks.js, search.js, stats.js, migrate.jsdata_list tool — browse stored entries with numbered summaries, optional search filterdata_delete tool — surgically remove individual entries by indexdata_manage tool (stats, export, prune by age, clear per-store)project filter to full_context_recalllimit param to decision_search and dead_end_searchSESSION_FORGE_STALE_HOURSschema_version to data files for future migration supportMIT
session-forge is NOT affiliated with SessionForge LLC (sessionforge.dev).
session-forge was first published on npm on February 7, 2026 — before SessionForge LLC appeared. We have no connection to their product or company.
Here's why this matters: session-forge stores all your data locally on your machine as plain JSON files. Nothing leaves your computer. No accounts, no servers, no third parties.
Any service asking you to route your AI session data, coding habits, and terminal access through their servers should make you ask: who has access to that data, and what are they doing with it?
Your workflow, your decisions, your code — that's yours. It should stay on your machine, under your control. That's how session-forge was built and that's how it will stay.
Built by Jacob Terrell
Persistent memory and session intelligence for AI coding assistants. Zero config.
{ "mcpServers": { "io.github.420247jake-session-forge": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Session Forge läuft lokal über stdio.
Zuletzt geprüft: 2026-11-08. Persistent memory and session intelligence for AI coding assistants. Zero config.