Menu
Introduction

Quick Start Guide

Quick Start Guide

Get MSP running in minutes. Choose your path based on your needs.

Choose Your Implementation

🚀 MSP Lite (Recommended for Starting)

Time: 5 minutes Perfect for: Vibe Coders with little coding knowledge, trying MSP, small projects
Includes: Core R³ protocol, local state, zero dependencies

🏢 Full Stack

Time: 30 minutes
Perfect for: Experienced developers, complex projects, production use
Includes: Neo4j integration, Obsidian sync, Linear tracking (or the equivalents of your choice!)

MSP Lite - Start in 5 Minutes

The fastest way to experience MSP's power. Zero dependencies, full context engineering.

1. Install MSP Lite

Download the scripts and add the MSPLite scripts to the root folder of your project. Further instructions for this step are on github

2. Start Your First Session

.\msp.ps1 start

# Output:
# 🚀 MSP Session Started (Lite Mode)
# 📁 State: .msp/current-session.json
# 🎯 Project: my-project
# 📊 Progress: 0%
# 
# Ready to track your work!

3. Track Your Work

# Update progress as you work
.\msp.ps1 update "Created user model" 10
.\msp.ps1 update "Added authentication" 25
.\msp.ps1 decide "Using JWT for stateless auth"

# Check current status anytime
.\msp.ps1 status

4. End Session with Context

.\msp.ps1 end

# Output:
# 📊 Session Summary
# ==================
# Duration: 2.5 hours
# Progress: 0% → 25% (+25%)
# Updates: 3
# Decisions: 1
# 
# Context saved to: .msp/sessions/2025-07-20-093042.json
# 
# Use '.\msp.ps1 recall' to restore this context

5. Experience the Magic

# Next day...
.\msp.ps1 start

# MSP automatically recalls your context:
# 🧠 Previous session detected!
# 📅 Last work: Yesterday (2.5 hours)
# 📊 Progress: 25%
# 💡 Last decision: "Using JWT for stateless auth"
# 🎯 Continue from: "Added authentication"

That's it! You're now using real-time context engineering. Your work is tracked, decisions are recorded, and context persists between sessions.

Full Stack - Complete Implementation

Set up MSP with all integrations for team-scale context engineering.

Prerequisites

  • PowerShell 7+ (cross-platform)
  • Neo4j Desktop or Docker
  • Obsidian (optional)
  • Linear account (optional)

1. Clone and Setup

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

# Run the setup wizard
.\scripts\setup-msp.ps1

# The wizard will:
# ✓ Check prerequisites
# ✓ Configure Neo4j connection
# ✓ Set up Obsidian vault path
# ✓ Configure Linear API
# ✓ Create initial schema

2. Configure Your Environment

# Set your project details
.\msp.ps1 config project.name "My Awesome Project"
.\msp.ps1 config project.repo "github.com/myteam/project"
.\msp.ps1 config user.name "Your Name"

# View all configuration
.\msp.ps1 config show

3. Initialize Neo4j Schema

# Create the knowledge graph structure
.\scripts\setup-neo4j.ps1

# This creates:
# - Session nodes
# - Decision nodes
# - Progress relationships
# - Entity tracking
# - Blocker management

4. Test the Integration

# Run a test session
.\msp.ps1 test

# Verifies:
# ✓ Neo4j connection
# ✓ Obsidian vault access
# ✓ Linear API
# ✓ State persistence

5. Start Using Full MSP

.\msp.ps1 start

# Full stack mode provides:
# 🔗 Neo4j knowledge graph
# 📝 Obsidian daily notes
# 📋 Linear issue updates
# 🤖 AI context export
# 📊 Team analytics

Integration Features

Neo4j Knowledge Graph

// View your session history
MATCH (s:Session)-[:HAS_UPDATE]->(u:Update)
WHERE s.user = 'Your Name'
RETURN s, u
ORDER BY u.timestamp DESC

Obsidian Daily Notes

# 2025-07-20 MSP Session

## Morning Session (09:30 - 12:00)
- Progress: 25% → 40%
- Completed user authentication
- Decision: JWT with refresh tokens

## Blockers
- [ ] Stripe webhook validation failing

Linear Integration

  • Automatic issue updates
  • Progress tracking on epics
  • Session summaries in comments

Next Steps

For MSP Lite Users

  1. Use it for a week to build the habit
  2. Export your context for AI assistance
  3. Consider upgrading to Full Stack for Knowledge Graph and full real-time Context Engineering

For Full Stack Users

  1. Read the Protocol Guide to master R³
  2. Set up your usage conventions
  3. Integrate with your CI/CD pipeline

Common Commands Reference

# Session Management
msp start                          # Start new session
msp update "message" [progress%]   # Track progress
msp end                           # End session
msp status                        # Current status
msp recall                        # Load previous context

# Decisions & Blockers
msp decide "decision text"        # Record decision
msp blocker "blocker description" # Track blocker
msp resolve "blocker resolution"  # Resolve blocker

# Context & Export
msp context                       # View full context
msp context | claude             # Pipe to AI
msp export --format json         # Export for tools

# Configuration
msp config show                   # View config
msp config set key value         # Update config
msp config reset                 # Reset to defaults

Troubleshooting Quick Fixes

"Session already active"

msp status          # Check current session
msp end --force     # Force end if stuck

"Neo4j connection failed"

msp test neo4j      # Test connection
msp config neo4j.uri "bolt://localhost:7687"

"Context not loading"

msp repair          # Rebuild from state files
msp recall --force  # Force reload

Ready for more? Check out real-world examples or dive into the full protocol specification.

MSP (Mandatory Session Protocol) - Context Engineering for Developers

Revolutionary context engineering tool that creates persistent knowledge graphs of your development work. Never lose context between coding sessions and make every AI interaction 10x more effective.

MSP Core Concepts

Deep dive into MSP's core concepts. Learn sessions, R³ protocol, knowledge graphs, and how context engineering transforms development productivity.