Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Session Forge

by 420247jakeversion 2.0.3i★ –iRuns on your computer
Registry nameio.github.420247jake/session-forge

Install

Overview

Description from the maker (original English)

Persistent memory and session intelligence for AI coding assistants. Zero config.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

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.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "session-forge": {
      "command": "npx",
      "args": [
        "-y",
        "session-forge"
      ]
    }
  }
}

Run this in your terminal

claude mcp add session-forge -- npx -y session-forge

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "session-forge": {
      "command": "npx",
      "args": [
        "-y",
        "session-forge"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "session-forge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "session-forge"
      ]
    }
  }
}

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 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account 420247jake, 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 7236 servers in this category
  • Published to the registry more recently than 5% of the other 7236 servers in this category
  • Basic checks equal to or better than 100% of the other 7236 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 Session Forge 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.0.3) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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

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 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 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 44 days 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.

session-forge

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, Windsurf, and any MCP-compatible client.


What it does

  • Session crash recovery — checkpoint your work, pick up where you left off
  • Decision logging — record why you chose X over Y, search it later
  • Dead end tracking — never repeat the same debugging mistake twice
  • User profile — AI remembers your name, preferences, and projects
  • Session journal — capture the journey, not just the task
  • Full context recall — bootstrap a new session with everything in one call
  • Data management — prune old entries, export all data, view stats

Quick start

Claude Code
claude mcp add session-forge -- npx session-forge
Cursor / Windsurf

Add to your MCP settings:

{

"mcpServers": { "session-forge": { "command": "npx", "args": ["-y", "session-forge"] } } }

That's it. No database, no Docker, no config files.


The 15 tools

Sessions
ToolDescriptionRequired
session_checkpointSave work-in-progress state for crash recoverytask, intent, next_steps
session_restoreCheck for interrupted work from a previous session—
session_completeArchive session and mark complete—
Profile
ToolDescriptionRequired
profile_getGet the current user profile—
profile_updateUpdate name, preferences, projects, or notes—
Journal
ToolDescriptionRequired
journal_entryRecord session summary with breakthroughs and frustrationssummary
journal_recallRetrieve recent session journals—
Decisions
ToolDescriptionRequired
decision_recordLog a significant decision with alternatives and reasoningchoice, reasoning
decision_searchSearch past decisions by keyword (supports limit param)query
Dead Ends
ToolDescriptionRequired
dead_end_recordLog a failed approach and the lesson learnedattempted, why_failed
dead_end_searchSearch past dead ends to avoid repeating mistakes (supports limit param)query
Context
ToolDescriptionRequired
full_context_recallGet everything — profile, journals, decisions, dead ends. Supports optional project filter.—
Data Management
ToolDescriptionRequired
data_managePrune old entries, export all data, clear stores, or view statsaction
data_listBrowse stored entries with numbered summaries. Supports search filter.store
data_deleteDelete a specific entry by index from data_list outputstore, entry_index

`data_manage` actions:

  • stats — entry counts and schema versions for all stores
  • export — dump all data as JSON
  • prune — 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:

  1. data_list with store="decisions" — see numbered list of all decisions
  2. data_list with store="decisions", query="minecraft" — filter by keyword
  3. data_delete with store="decisions", entry_index=3 — remove entry #3 from the list

Why session-forge?

session-forgeBasic memory MCPsEnterprise tools
Setupnpx session-forgeVariesDocker + databases
Dead end trackingYesNoNo
Decision loggingYesNoSome
Session crash recoveryYesSomeYes
Data managementYesNoSome
User profileYesSomeNo
Dependencies2 (SDK + zod)Varies5-10+
InfrastructureZero (plain JSON)SQLite/ONNX/Vector DBPostgreSQL + Redis
Tools15 focused4-937+

Configuration

Environment variables
VariableDefaultDescription
SESSION_FORGE_DIR~/.session-forge or %APPDATA%\session-forgeOverride data storage location
SESSION_FORGE_STALE_HOURS24Hours before an inactive session is auto-archived

Storage

All data is stored locally as plain JSON files:

PlatformLocation
Linux / macOS~/.session-forge/
Windows%APPDATA%\session-forge\

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.


CLAUDE.md template

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

Changelog

v2.0.1
  • Added disclaimer: session-forge is NOT affiliated with SessionForge LLC (sessionforge.dev)
v2.0.0
  • Knowledge Graph — link decisions and dead ends together with related_dead_ends and led_to_decision fields
  • Scored Search — fuzzy matching, tag filtering, AND/OR search modes, relevance scoring (replaces basic string matching)
  • Usage Stats — tracks dead ends avoided, searches performed, sessions recovered
  • MEMORY.md Sync — full_context_recall can read your MEMORY.md and suggest decisions/dead ends that should be saved to memory
  • Enhanced Checkpoints — now tracks errors_encountered, key_findings, decisions_made, dead_ends_hit
  • New storage modules: links.js, search.js, stats.js, migrate.js
  • Schema bumped to v2
v1.2.0
  • Added data_list tool — browse stored entries with numbered summaries, optional search filter
  • Added data_delete tool — surgically remove individual entries by index
  • Users can now see exactly what's stored and delete anything they want
v1.1.0
  • Added data_manage tool (stats, export, prune by age, clear per-store)
  • Added project filter to full_context_recall
  • Added limit param to decision_search and dead_end_search
  • Added error logging to JSON reads (was silently swallowing parse failures)
  • Added configurable stale session timeout via SESSION_FORGE_STALE_HOURS
  • Added schema_version to data files for future migration support
  • Fixed version mismatch between code and package.json
v1.0.2
  • Initial public release

License

MIT


Important Notice

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

Ask PopNx