MCP Changelog
All notable user-facing changes to LogicStamp MCP Server are tracked here. The project follows Semantic Versioning and a Keep a Changelog-style format.
This changelog is automatically fetched from the MCP GitHub repository.
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
0.1.2 - 2025-12-30
Changed
- Node.js Requirement Update - Updated minimum Node.js version requirement from >=18.0.0 to >=18.18.0 to align with
logicstamp-contextCLI requirements- Node 20+ is now recommended for best performance and features
- Updated all documentation, prerequisites, and integration guides
- Updated
package.jsonengines field
Added
- Depth Parameter Documentation - Added comprehensive recommendations for using
depth: 2with React/TypeScript projects- README.md - Added depth parameter guidance emphasizing
depth: 2recommendation for React projects (line 121)- Clarifies that LLM does NOT automatically detect when depth=2 is needed
- Explains that default depth=1 only includes direct dependencies
- docs/mcp_integration.md - Enhanced depth parameter documentation with React-specific recommendations (lines 76, 85)
- Added RECOMMENDED guidance to start with
depth: 2for React/TypeScript projects - Included example usage:
{ "projectPath": "...", "depth": 2 } - Explained that depth=2 captures nested components (e.g., App → Hero → Button)
- Added note that LLM must explicitly request depth=2 upfront
- Added RECOMMENDED guidance to start with
- docs/logicstamp-for-llms.md - Added critical depth parameter guidance (lines 44, 158-179)
- Added CRITICAL section recommending
depth: 2for React/TypeScript projects - Explained when depth=1 is insufficient (missing components, incomplete graphs)
- Added example code showing recommended usage pattern
- Clarified that LLM does NOT automatically detect when depth=2 is needed
- Added CRITICAL section recommending
- docs/startup-ritual.md - Updated startup ritual with depth=2 recommendations (lines 12-14, 51-55)
- Added RECOMMENDED guidance in startup workflow
- Included examples and when to use depth=2
- Explained difference between depth=1 (direct dependencies) and depth=2 (nested components)
- src/mcp/server.ts - Enhanced tool descriptions with depth=2 recommendations (lines 61-63, 88)
- Updated
logicstamp_refresh_snapshotdescription to recommend depth=2 for React projects - Added guidance about nested component hierarchies
- Clarified that depth=2 ensures nested components are included with contracts and styles
- Updated
- README.md - Added depth parameter guidance emphasizing
Fixed
- Version Consistency - Fixed version mismatches across codebase to ensure all version references match
package.json- README.md - Updated version badge from
0.1.1to0.1.2(line 13)- Badge now correctly displays current package version
- src/mcp/server.ts - Updated server version from
0.1.0to0.1.2(line 30)- MCP server now reports correct version to clients
- Fixes discrepancy where server reported older version than package
- docs/mcp_integration.md - Updated example config version from
0.1.0to0.1.2(line 852)- Example MCP server configuration now shows correct version
- Ensures documentation examples match actual implementation
- All version references now consistently match
package.jsonversion0.1.2 - Prevents confusion when users check version information across different sources
- README.md - Updated version badge from
0.1.1 - 2025-12-14
Fixed
- Documentation Fix - Corrected
projectPathparameter documentation forlogicstamp_refresh_snapshot- Updated docs to correctly mark
projectPathas required (was incorrectly marked as optional) - Added explanation of why
projectPathis required (prevents hangs whenstamp inithas been run) - Updated all examples to include
projectPathparameter - Fixes issue where users following documentation would encounter errors when omitting
projectPath
- Updated docs to correctly mark
0.1.0 - 2025-12-13
Added
Core Features
- MCP Server Implementation - Full Model Context Protocol server for LogicStamp Context
- Snapshot Management - In-memory snapshot state management with automatic cleanup (1-hour TTL)
- 6 MCP Tools - Complete tool suite for codebase analysis:
logicstamp_refresh_snapshot- Create snapshots of codebase statelogicstamp_list_bundles- List available component bundleslogicstamp_read_bundle- Read full component contracts and dependency graphslogicstamp_compare_snapshot- Detect changes after edits (drift detection)logicstamp_compare_modes- Generate token cost comparisons across modeslogicstamp_read_logicstamp_docs- Access LogicStamp documentation
Analysis Capabilities
- Component Contract Extraction - Extract props, state, hooks, and dependencies
- Style Metadata Support - Extract Tailwind classes, SCSS modules, framer-motion animations, color palettes, layout patterns
- Dependency Graph Analysis - Understand component relationships
- Token Optimization - Configurable code inclusion modes (none/header/full)
- Multiple Analysis Profiles - Support for
llm-chat,llm-safe, andci-strictprofiles
Developer Experience
- Comprehensive Documentation - README, quick start guide, integration guides, API reference
- Integration Guides - Setup instructions for Claude CLI, Claude Desktop, and Cursor IDE
- Example Configurations -
.claude.json.exampleand.mcp.json.examplefiles - TypeScript Support - Full type safety with comprehensive type definitions
- Error Handling - Proper MCP error codes and descriptive error messages
Testing & Quality
- Test Suite - 150 tests covering unit, integration, and E2E scenarios
- CI/CD Pipeline - GitHub Actions workflow testing on Ubuntu, Windows, and macOS
- Multi-Node Testing - CI tests on Node.js 18.x and 20.x
- Type Checking - TypeScript compilation verification in CI
Documentation
- Quick Start Guide - Get up and running in minutes
- Startup Ritual - Recommended workflow for AI assistants
- MCP Integration Guide - Complete API reference and architecture documentation
- Tool Descriptions - Detailed documentation for each MCP tool
- Troubleshooting Guide - Common issues and solutions
- Contributing Guidelines - Guide for contributors
- Security Policy - Security reporting and best practices
Configuration
- Example Config Files - Ready-to-use configuration templates
- Flexible Project Paths - Support for custom project paths
- Baseline Comparison - Compare against disk or snapshot baselines
- Smart Cache Cleanup - Automatic detection and cleanup of corrupted
.logicstampcache directories- Detects invalid JSON in
context_main.json - Detects stale project paths in cache metadata files
- Preserves cache when healthy for improved performance
- Detects invalid JSON in
forceRegenerateParameter - Added tologicstamp_compare_snapshottool- When
false(default): Fast comparison using existingcontext_main.jsonfrom disk - When
true: Regenerates context before comparing to ensure fresh data
- When
cleanCacheParameter - Added tologicstamp_refresh_snapshot,logicstamp_compare_snapshot, andlogicstamp_compare_modestools- Manual override to force cache cleanup
- Works alongside automatic corruption detection
Changed
- Improved Error Handling - Better error messages for missing
context_main.jsonfiles- Clear guidance when context files are missing
- Suggests using
forceRegenerate: trueor runninglogicstamp_refresh_snapshotfirst
- Enhanced
logicstamp_compare_snapshotTool - More flexible regeneration control- Independent control over regeneration (
forceRegenerate) and style inclusion (includeStyle) - Better documentation of when each parameter takes effect
- Independent control over regeneration (
Fixed
- Cache corruption issues that could cause analysis failures
- Path mismatch detection for projects moved or renamed
Technical Details
- Dependencies:
@modelcontextprotocol/sdk@^1.24.0 - Node.js Support: >=18.18.0 (Node 20+ recommended)
- License: MIT
- Read-Only Design: Server never modifies project files directly
Notes
- This is the initial public release
- Requires
logicstamp-contextCLI to be installed globally (npm install -g logicstamp-context) - All tools are read-only - they analyze but never modify your codebase