Skip to main content
Glama

DollhouseMCP

by DollhouseMCP
NEXT_SESSION_STARTUP_GUIDE.md3.48 kB
# Next Session Startup Guide ## 🚀 Quick Status Check ```bash cd /Users/mick/Developer/MCP-Servers/DollhouseMCP git status npm test -- --testNamePattern="logger" --no-coverage # Verify logger tests pass ``` ## 📍 Current State (July 10, 2025 Evening) - **Latest Release**: v1.2.4 - Fixed MCP protocol compatibility - **NPM Package**: @mickdarling/dollhousemcp@1.2.4 (missing personas) - **User Status**: Successfully using npm installation with manual persona copy ## 🔧 Immediate Tasks ### 1. Fix NPM Package to Include Personas ```bash # Check current .npmignore status cat .npmignore | grep personas # Should show: # personas/ # Include personas in npm package # Verify personas will be included npm pack --dry-run | grep personas ``` ### 2. Release v1.2.5 with Personas ```bash # Update version npm version patch # Will bump to 1.2.5 # Build and publish npm run build npm publish # Create GitHub release gh release create v1.2.5 --title "v1.2.5 - Include Default Personas" --notes "..." ``` ### 3. Test NPM Installation ```bash # Test fresh install npm uninstall -g @mickdarling/dollhousemcp npm install -g @mickdarling/dollhousemcp@1.2.5 # Verify personas included ls -la $(npm root -g)/@mickdarling/dollhousemcp/personas/ ``` ## 📝 Key Information ### File Locations - **Dev**: `/Users/mick/Developer/MCP-Servers/DollhouseMCP/` - **NPM Global**: `/opt/homebrew/lib/node_modules/@mickdarling/dollhousemcp/` - **Claude Config**: `~/Library/Application Support/Claude/claude_desktop_config.json` ### Recent PRs & Issues - **PR #189**: MCP protocol fix (merged) - **Issue #190**: Logger enhancements (created) - **Issue #188**: Path resolution follow-ups ### What We Fixed Today 1. ✅ Console output breaking MCP protocol 2. ✅ Docker tests failing due to console checks 3. ✅ User's JSON config merge issues 4. ✅ Missing personas in npm package (manual fix) ### What Needs Fixing 1. ⏳ Include personas in npm package (v1.2.5) 2. ⏳ Logger enhancements (Issue #190) 3. ⏳ Update setup.sh for npm users ## 🎯 Quick Commands ### Check Everything Works ```bash # Run all tests npm test # Check specific problem areas npm test -- --testNamePattern="logger" npm test -- --testNamePattern="Docker" # Check npm package contents npm pack --dry-run | grep -E "personas|\.md" ``` ### Release Process ```bash # Standard release flow git pull origin main npm version patch npm run build npm publish git push origin main --tags gh release create v1.2.X --title "..." --notes "..." ``` ## 💡 Context from Today ### Logger Key Points - Suppresses output after MCP connection (`setMCPConnected()`) - Uses circular buffer (1000 entries max) - NODE_ENV check must be inside log method (not at module level) - All console calls replaced with logger ### User Pain Points - JSON config merging is confusing - NPM installation didn't include personas - Need clear visual guides for configuration ### Success Metrics - User confirmed working with npm install - All tests passing (500 total) - Docker tests fixed - MCP protocol no longer broken ## 🔗 Reference Documents - `docs/session-history/2025/07/SESSION_SUMMARY_JULY_10_2025_EVENING.md` - `docs/JSON_MERGE_GUIDE.md` - `docs/session-history/2025/07/PR_189_TEST_FAILURE_ANALYSIS.md` ## Remember - User is on Pacific time (Thursday evening, July 10) - They use npm global installation, not local dev - They have both whois and dollhousemcp MCP servers - JSON merging is a common user pain point

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DollhouseMCP/DollhouseMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server