shopdb-flask/.claude/maintenance/DEV-STARTUP-CHECKLIST.md

Flask-ShopDB Dev Environment Startup Checklist

Quick reference for starting the complete development environment with all MCP servers and multi-agent collaboration.

---

Pre-Launch (First Time Only)

These items are already configured and will persist:

• ✅ .mcp.json - MCP server configurations (gortex, mysql, browser, vm, coordinator)
• ✅ .claude/settings.json - Auto-enables project MCP servers + SessionEnd hook
• ✅ start-dev.cmd - Updated with NODE_TLS_REJECT_UNAUTHORIZED=0 for Vite
• ✅ stop-dev.cmd - Auto-runs when Claude Code session closes

---

Launch Sequence

Step 1: Start Development Environment

./start-dev.cmd

What this does:

1. Checks MCP Coordinator daemon - starts it if not running (for multi-agent collaboration)
2. Starts Flask API (Docker) - https://192.168.100.1:5001
3. Starts MySQL DB (Docker) - healthy check
4. Starts Vite dev server - http://192.168.100.1:5173
   • Note: Vite window will pop up (this is normal)
   • Vite now has NODE_TLS_REJECT_UNAUTHORIZED=0 to connect to Flask's HTTPS

Verify it's running:

• Frontend: http://192.168.100.1:5173
• Backend: https://192.168.100.1:5001

---

Step 3: Open Claude Code Session

# In project directory
claude

On first launch after MCP config changes, you'll be prompted to approve:

• ✅ gortex (C:\Users\270015376\Documents\gortex.exe)
• ✅ mysql (database access)
• ✅ browser (browser automation)
• ✅ vm / vm-shopfloor (SSH to test VM)
• ✅ coordinator (multi-agent collaboration)

Auto-loaded MCP servers:

• github, shopdb, amber (from user config)
• Plus all project servers from .mcp.json

---

What's Automated

On Dev Environment Start (./start-dev.cmd):

• ✅ MCP Coordinator daemon auto-starts (if not already running)
• ✅ Flask API (Docker)
• ✅ MySQL DB (Docker)
• ✅ Vite dev server (with TLS fix)

On Claude Code Session Start:

• ✅ All approved MCP servers auto-connect
• ✅ enableAllProjectMcpServers: true loads project servers

On Session Close:

• ✅ ./stop-dev.cmd runs automatically (SessionEnd hook)
• ✅ MCP Coordinator daemon stops
• ✅ Docker containers stop
• ✅ Vite dev server stops
• ✅ No manual cleanup needed

---

Troubleshooting

Vite Proxy Errors (TLS)

If you see http proxy error: /api/... in Vite window:

• Check Vite was started with NODE_TLS_REJECT_UNAUTHORIZED=0
• Restart Vite: Kill the window, run ./start-dev.cmd again

MCP Servers Not Loading

• Restart Claude Code session
• Check .mcp.json exists in project root (not .claude/mcp-servers.json)
• Verify enableAllProjectMcpServers: true in .claude/settings.json

Coordinator Not Working

# Check daemon status
npx mcp-coordinator server status

# Restart if needed
npx mcp-coordinator server stop
npx mcp-coordinator server start --daemon

Flask Not Responding

# Check Docker containers
docker ps --filter "name=flask-shopdb"

# Restart if needed
./stop-dev.cmd
./start-dev.cmd

---

Quick Status Check

# Check all services at once
docker ps --filter "name=flask-shopdb" && \
curl -s http://localhost:5173 > /dev/null && echo "✅ Vite OK" && \
curl -sk https://localhost:5001/api/auth/me 2>&1 | grep -q "Authorization" && echo "✅ Flask OK" && \
curl -s http://localhost:3100/health > /dev/null && echo "✅ Coordinator OK"

---

Login Credentials

ShopDB App:

• Username: 270015376 or testadmin
• Password: admin123

Test VM (192.168.100.10):

• SupportUser: vos313
• shopfloor: vos313

---

Current MCP Servers

Server	Purpose	Status
github	GitHub API access	Auto-loaded
shopdb	ShopDB-specific tools	Auto-loaded
amber	GE internal tools	Auto-loaded
gortex	Custom Gortex tool	Needs approval
mysql	Direct DB access	Needs approval
browser	Browser automation	Needs approval
vm	SSH to test VM (SupportUser)	Needs approval
vm-shopfloor	SSH to test VM (shopfloor)	Needs approval
coordinator	Multi-agent collaboration	Needs approval

---

Last updated: 2026-09-10