Patch Notes 📝

Keep your coding tutorials and StackOverflow claims up-to-date against modern documentation.

---

🚀 Overview

Many developer tutorials, guides, and StackOverflow answers become outdated as libraries release breaking changes. Patch Notes solves this by ingesting both tutorial media (videos/URLs) and official documentation into a local semantic database. It compares video claims with current docs, highlighting obsolete APIs, deprecated functions, and code syntax changes side-by-side.

---

🧠 How this uses Supermemory Local

Patch Notes relies on a self-hosted Supermemory Local server instance running containerized on port 6767 for all core indexing, vector embedding storage, and query retrieval.

• Chronological Provenance Graph: Tutorial transcriptions and official markdown documents are loaded into a unified Supermemory graph index scoped under a slugified containerTag per topic.
• Smart Comparison: Rather than performing a standard text diff, Patch Notes queries Supermemory's hybrid retrieval system to extract historical claims and uses its metadata scoping to determine the current, contradiction-resolved truth.
• Model Context Protocol (MCP): The entire freshness checking pipeline is exposed as a local MCP server, allowing external coding assistants to query the local Supermemory facts directly.

---

🛠️ Windows & Docker Architecture

The official Supermemory local installation script requires a native Linux shell environment. To maintain complete local data sovereignty on Windows without native bash installation, we run the authentic pre-compiled Linux binary (supermemory-server-linux-x64) inside a Debian-based Docker container. This allows the Next.js SDK client to communicate with the real self-hosted Supermemory engine over standard TCP port 6767.

---

📦 Setup & Installation

1. Prerequisite: Start Docker Desktop

Make sure Docker Desktop is running on your machine.

2. Start Supermemory Local Container

Start the pre-built supermemory-local container on port 6767:

docker start supermemory-server

(If starting from scratch for the first time):

docker run -d --name supermemory-server -p 6767:6767 -v supermemory-data:/root/.supermemory -e GEMINI_API_KEY="your_api_key_here" supermemory-local

3. Install Project Dependencies

npm install

4. Configure Environment Variables

Create a .env.local file in the root of the project:

SUPERMEMORY_API_KEY=sm_jnNpbt8zsALUqAJpyZZYd1_vZoQdujWsl7sINc7Dqx2sIm5F63B6VHIRi73ZOOSHJmdxHsw5UFfZNWQ0j9Np12U
SUPERMEMORY_BASE_URL=http://localhost:6767
GEMINI_API_KEY=your_gemini_api_key_here

5. Run the Web Application

npm run dev

Open http://localhost:3000 to access the dashboard.

Note

The npm run dev script is configured with the --webpack flag inside package.json to bypass folder-scanning and tracing hangs on Windows development hosts.

---

🔌 Connecting the MCP Server

You can query Patch Notes' facts directly inside your favorite AI coding assistant.

Important

Configuration Path: When configuring the servers below, make sure to replace C:/Users/priya/OneDrive/Desktop/patch-notes with the absolute path of your own project clone.

Antigravity Config (C:\Users\priya\.gemini\config\mcp_config.json)

{
  "mcpServers": {
    "patch-notes": {
      "command": "npx",
      "args": ["tsx", "C:/Users/priya/OneDrive/Desktop/patch-notes/src/mcp-server/server.ts"],
      "env": {
        "SUPERMEMORY_API_KEY": "sm_jnNpbt8zsALUqAJpyZZYd1_vZoQdujWsl7sINc7Dqx2sIm5F63B6VHIRi73ZOOSHJmdxHsw5UFfZNWQ0j9Np12U",
        "SUPERMEMORY_BASE_URL": "http://localhost:6767",
        "GEMINI_API_KEY": "your_gemini_api_key_here"
      }
    }
  }
}

Claude Code Config (.mcp.json in project root)

{
  "mcpServers": {
    "patch-notes": {
      "command": "npx",
      "args": ["tsx", "C:/Users/priya/OneDrive/Desktop/patch-notes/src/mcp-server/server.ts"],
      "env": {
        "SUPERMEMORY_API_KEY": "sm_jnNpbt8zsALUqAJpyZZYd1_vZoQdujWsl7sINc7Dqx2sIm5F63B6VHIRi73ZOOSHJmdxHsw5UFfZNWQ0j9Np12U",
        "SUPERMEMORY_BASE_URL": "http://localhost:6767",
        "GEMINI_API_KEY": "your_gemini_api_key_here"
      }
    }
  }
}

---

🧪 Testing the MCP Server

You can verify the stdio-based MCP tool calls directly from your terminal using the provided test harness script:

npx tsx scratch/test-mcp.ts

This script automatically seeds the local database, initializes the server subprocess, and triggers check_tutorial_freshness over stdin, printing the formatted JSON-RPC response to your console.

---

🎥 Demo Video

Watch the demo video presentation