Never lose context again. A developer productivity tool for the context engineering era.

MSP (Mandatory Session Protocol) is a model for context engineering that ensures you never lose track of your development work. It enforces structured session management across your entire toolchain, creating a persistent knowledge graph of your project's evolution.

Vibe Coding (noun): The practice of using AI assistants through unstructured, conversational interactions without persistent context, resulting in:

• 🤯 Context Amnesia: Every conversation starts from zero
• 🔄 Repeated Work: " Context hallucination results in code debt
• 🤖 Shallow AI Help: "Let me explain my entire project again..."
• 📉 Inconsistent responses: Different answers to similar questions
• Lost decisions: You've switched integration but your AI assistant only remembers the old one

Start new chat → Explain context → Get answer → Close chat → Forget everything → Repeat

Context Engineering (noun): The systematic practice of capturing, structuring, and maintaining development context to enable deep, consistent, and evolving AI assistance.

MSP implements the looping *R³ Framework (Route-Recall-Record) to create a memory-augmented development workflow:

    ROUTE → RECALL → RECORD
      ↑                    ↓
      └────────────────────┘

Zero dependencies. Just PowerShell.

# Download and start
iwr -Uri "https://github.com/msp-model/msp/raw/main/lite/msp-lite.ps1" -OutFile "msp.ps1"
.\msp.ps1 start

Full context engineering with Neo4j, Obsidian, and Linear.

NOTE: You can switch any of these out for your tool of choice. The important thing is to have all three functions covered. Go to http://sessionprotocol.dev to find out more.

# Clone and setup
git clone https://github.com/msp-model/msp-model.git
cd msp/standard
.\setup.ps1

Enterprise features, team collaboration, custom integrations.

Every session, decision, and progress update becomes a queryable node in Neo4j. Your project's entire history at your fingertips.

Feed complete project context to any AI with one command. Claude, GPT, or Copilot get instant understanding.

Quantify your work with granular progress updates. Know exactly where you are and what's next.

Never wonder "why did we do it this way?" again. Every architectural choice is documented with rationale.

Start where you left off with complete context.

• Neo4j: Knowledge graph and relationships
• Obsidian: Markdown documentation
• Linear: Issue tracking and planning
• Git: Version control integration

.\msp.ps1 start

# MSP loads your context:
# → Current project state
# → Recent decisions
# → Active blockers
# → Progress metrics

.\msp.ps1 update "Implemented OAuth flow" 45
.\msp.ps1 decide "Using JWT with 15min expiry - better security"
.\msp.ps1 block "CORS issues with refresh endpoint"

.\msp.ps1 end

# MSP saves everything:
# → Session duration and progress
# → All decisions with rationale
# → Generated Neo4j queries
# → Updated documentation
# → Automated validation across the three tools - knowledge graph, task/project management and documentation - ensures everything is in sync and errors are not creeping in.

• Concepts

  • Context Engineering - Why MSP exists
  • The R³ Protocol - Route, Recall, Record
  • Why MSP - Philosophy and principles

• Guides

  • Quickstart - Get running in 5 minutes
  • Configuration - Customize MSP
  • Troubleshooting - Common issues

• API Reference

  • Commands - All MSP commands
  • State Structure - Data format
  • Integration API - Extend MSP

Check the examples/ directory for real-world usage:

• solo-developer/ - Individual productivity workflows
• small-team/ - Team collaboration patterns (COMING SOON)
• enterprise/ - Large-scale implementations (COMING SOON)

We welcome contributions! See CONTRIBUTING.md for guidelines.

# Clone the repo
git clone https://github.com/msp-model/msp-model.git
cd msp-model

MSP is open source under the MIT License.

Ready to never lose context again?

# Your journey starts here
.\msp.ps1 start