MSP (Mandatory Session Protocol) - Context Engineering for Developers

What is MSP?

MSP (Mandatory Session Protocol) is a context engineering tool that creates a persistent knowledge graph of your development work. It ensures you never lose context between coding sessions, making every AI interaction 10x more effective.

MSP transforms "vibe coding" into structured, trackable progress with complete context persistence.

The Problem

'Traditional' AI-Assisted development workflows suffer from:

🤯 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

The Solution: Context Engineering

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

MSP is a model for 'Real-Time' Context Engineering, by implementing the continuous R³ Protocol (Route-Recall-Record) to maintain (near) perfect context throughout and between development sessions:

Route

Know where you're going with clear objectives and waypoints

Recall

Instantly restore previous context and decisions

Record

Capture every decision, progress update, and insight

How It Works

Start Your Session

Initialize MSP to load your project context:

.\msp.ps1 start

Track Your Work

Record progress and decisions as you code:


.\msp.ps1 update "Implemented JWT authentication" 25
.\msp.ps1 decide "Using Redis for session storage" >

Export Context

Generate complete context for AI assistants:

.\msp.ps1 context --format ai | clip

Core Features

Every session, decision, and entity becomes a queryable node in Neo4j:

MATCH (s:Session)-[:MADE_DECISION]->(d:Decision)
WHERE s.project = 'my-project'
RETURN d.content, d.rationale
ORDER BY d.timestamp DESC

Quantify your work with granular progress updates:

Track progress percentage (0-100%)
Measure session duration
Identify productivity patterns
Generate sprint reports

Export complete project context for any AI:

PROJECT: E-commerce API
LANGUAGE: TypeScript
DECISIONS: 47 tracked
CURRENT: Payment integration
BLOCKERS: Webhook validation

Why MSP?

Transform Your Development Workflow

87% Less Context Loss: Never repeat yourself
3x Faster AI Responses: Complete context = better answers
100% Decision History: Every choice documented

Integration Ecosystem

MSP seamlessly integrates with your existing tools:

Tool	Purpose	Integration
Neo4j	Knowledge Graph	Session relationships & queries
Obsidian	Documentation	Daily notes & decision records
Linear	Project Management	Epic tracking & progress sync
Claude/GPT	AI Assistance	Context-aware responses

Quick Example

Here's MSP in action during a typical development session:

# Monday morning - instantly back in context
.\msp.ps1 start

>>> Loading context...
>>> Last session: Implementing Stripe webhooks
>>> Current blocker: Signature validation
>>> Next task: Add retry logic

# Continue exactly where you left off!

Next Steps
<Cards>
  <Card 
    title="Quick Start" 
    href="/docs/introduction/quickstart"
    description="Get MSP running in 5 minutes"
  />
  <Card 
    title="Installation" 
    href="/docs/setup/installation"
    description="Set up MSP with your tools"
  />
  <Card 
    title="Examples" 
    href="/docs/introduction/examples"
    description="See MSP in real projects"
  />
</Cards>

<Callout>
  Ready to stop losing context? [Install MSP](/docs/introduction/quickstart) and start engineering your context today.
</Callout>

Menu