@programinglive/dev-workflow-mcp-server 1.7.10 → 1.7.12

package/.dockerignore

@@ -0,0 +1,60 @@
+# Node modules - will be installed in container
+node_modules
+npm-debug.log
+yarn-error.log
+
+# Git files
+.git
+.gitignore
+.gitattributes
+
+# Environment files
+.env
+.env.local
+.env.*.local
+
+# Development files
+*.log
+*.pid
+*.seed
+*.pid.lock
+
+# IDE files
+.vscode
+.idea
+*.swp
+*.swo
+*~
+
+# Test files
+tests
+*.test.js
+coverage
+
+# Documentation
+docs
+*.md
+!README.md
+
+# CI/CD
+.github
+.husky
+
+# Build artifacts
+dist
+build
+.cache
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# Web frontend (if not needed in container)
+web/node_modules
+web/dist
+web/.next
+
+# Docker files
+Dockerfile
+docker-compose*.yml
+.dockerignore

package/.env.example

@@ -0,0 +1,12 @@
+# Database Configuration
+# Supported types: sqlite, mysql, postgres
+DEV_WORKFLOW_DB_TYPE=sqlite
+
+# Connection URLs
+# MySQL Example: mysql://user:password@localhost:3306/database
+# Postgres Example: postgres://user:password@localhost:5432/database
+# Postgres Docker Example: postgres://devworkflow:password@postgres:5432/devworkflow
+DEV_WORKFLOW_DB_URL=
+
+# Optional: Override user ID 
+# DEV_WORKFLOW_USER_ID=my-custom-user-id

package/.env.production

@@ -0,0 +1,16 @@
+# Production Environment Configuration for Docker Deployment
+# Copy this file to .env on your GCP instance
+
+# Database Configuration
+DEV_WORKFLOW_DB_TYPE=postgres
+DEV_WORKFLOW_DB_URL=postgres://devworkflow:YOUR_SECURE_PASSWORD_HERE@postgres:5432/devworkflow
+
+# PostgreSQL Password (used by docker-compose)
+# IMPORTANT: Change this to a secure password!
+POSTGRES_PASSWORD=YOUR_SECURE_PASSWORD_HERE
+
+# Optional: User ID for multi-user environments
+# DEV_WORKFLOW_USER_ID=your-username
+
+# Node Environment
+NODE_ENV=production

package/CHANGELOG.md

@@ -2,6 +2,51 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+### [1.7.12](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.7.11...v1.7.12) (2025-12-17)
+
+
+### 📝 Documentation
+
+* post-release cleanup v1.7.11 ([c2ee733](https://github.com/programinglive/dev-workflow-mcp-server/commit/c2ee733bb9ec21e6ad39e564aa1fc315ca79cff6))
+
+
+### ✨ Features
+
+* add authentication system with login page and protected routes ([2acb20e](https://github.com/programinglive/dev-workflow-mcp-server/commit/2acb20efb25cddb3d2b6ee80427310c3315582dc))
+* add Docker deployment support with PostgreSQL for GCP ([3adb4cb](https://github.com/programinglive/dev-workflow-mcp-server/commit/3adb4cb9ace571faf7f2138634481362c24f2730))
+* expose PostgreSQL port for remote access ([b1d4066](https://github.com/programinglive/dev-workflow-mcp-server/commit/b1d40665a1c01960184508d53c0bec0b5c051e4b))
+* revamp history page UI and remove history from landing ([a9d0e4e](https://github.com/programinglive/dev-workflow-mcp-server/commit/a9d0e4e70b8aa5ed3457f661cb3dbdca2d8d2a30))
+* simplify docker-compose to only PostgreSQL, improve logout button UI ([4530862](https://github.com/programinglive/dev-workflow-mcp-server/commit/4530862b33178d6391ee294f74ef222843f5d5a4))
+
+
+### 🐛 Bug Fixes
+
+* suppress 401 auth errors in console ([b63e63b](https://github.com/programinglive/dev-workflow-mcp-server/commit/b63e63b60a4ba8236db1848a77d2f39f49e644b3))
+* **web:** resolve 500 error on history API and auth sync ([88bbff0](https://github.com/programinglive/dev-workflow-mcp-server/commit/88bbff043f99e06a7b8ed9b9789d87d22e1f9035))
+
+
+### 🧹 Chores
+
+* configure commitlint and husky via commiter setup ([4de6c84](https://github.com/programinglive/dev-workflow-mcp-server/commit/4de6c8400b6869503bee8407bb23266779133144))
+* update website to v1.7.11 and fix dependencies ([da80b1c](https://github.com/programinglive/dev-workflow-mcp-server/commit/da80b1c9d5bdf10e1387d4b2d1e98b8d2fee5e92))
+
+### [1.7.11](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.7.10...v1.7.11) (2025-12-16)
+
+
+### 📝 Documentation
+
+* fix version status in PRD ([fa7912b](https://github.com/programinglive/dev-workflow-mcp-server/commit/fa7912ba3354a88ce943fbc9a0f34f4bd1936e34))
+
+
+### ✨ Features
+
+* implement .env support and fix mysql date persistence ([096797c](https://github.com/programinglive/dev-workflow-mcp-server/commit/096797c689813f44106a027cfa36e90d3da4bfb4))
+
+
+### ✅ Tests
+
+* comprehensive DB adapter tests, env support, and warning fixes ([44814ff](https://github.com/programinglive/dev-workflow-mcp-server/commit/44814ffcc0a1efbc8e89948de22c3b196834b390))
+
 ### [1.7.10](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.7.9...v1.7.10) (2025-12-16)
 
 

package/Dockerfile

@@ -0,0 +1,32 @@
+# Multi-stage build for dev-workflow MCP server
+FROM node:20-alpine AS base
+
+# Install build dependencies for native modules (better-sqlite3, pg)
+RUN apk add --no-cache python3 make g++ postgresql-client
+
+WORKDIR /app
+
+# Copy package files
+COPY package*.json ./
+
+# Install dependencies (skip postinstall since we don't need state files at build time)
+RUN npm ci --only=production --ignore-scripts
+
+# Copy application code
+COPY . .
+
+# Create data directory for workflow state
+RUN mkdir -p /app/data && \
+    chown -R node:node /app
+
+# Switch to non-root user
+USER node
+
+# Set environment variables
+ENV NODE_ENV=production
+ENV DEV_WORKFLOW_DB_TYPE=postgres
+
+# The MCP server runs on stdio, no port exposure needed
+# Communication happens via stdin/stdout
+
+CMD ["node", "index.js"]

package/README.md

@@ -62,6 +62,26 @@ Plesk supports Node.js applications through its Node.js extension. To deploy the
 
 > **Important:** MCP clients (Windsurf, Claude Desktop, etc.) must launch the server process locally via stdio. Hosting the dashboard on a public domain does **not** expose the MCP interface. Without SSH or another way to execute `node index.js` on the server, users cannot connect their MCP clients to the hosted instance.
 
+### Option 4: Deploy with Docker on Google Cloud
+
+Deploy the MCP server to Google Cloud Compute Engine using Docker and PostgreSQL for a production-ready, cloud-hosted setup.
+
+**Quick Start:**
+1. SSH into your GCP instance
+2. Run the setup script: `bash scripts/setup-gcp-instance.sh`
+3. Clone the repository and configure `.env`
+4. Start containers: `docker-compose up -d`
+5. Update your local MCP client config to connect via SSH
+
+**Benefits:**
+- ✅ PostgreSQL database for robust data persistence
+- ✅ Containerized deployment for consistency
+- ✅ Remote access via SSH tunneling
+- ✅ Easy updates and rollbacks
+
+See the [GCP Deployment Guide](./docs/GCP_DEPLOYMENT.md) for complete step-by-step instructions.
+
+
 #### Two Usage Modes
 
 - **Local (source)**: Point your MCP client to `index.js`. This runs directly from source and requires no build step. Recommended for MCP usage.
@@ -183,9 +203,23 @@ See [Antigravity Getting Started](./docs/antigravity/GETTING-STARTED.md) for det
 
 ## ⚙️ Configuration
 
-### Database Backend
+### Database Setup
 
-By default, the server uses a local **SQLite** database stored in `.state/dev-workflow.db`. You can switch to **MySQL** or **PostgreSQL** for centralized storage using environment variables.
+The server supports **SQLite** (default), **MySQL**, and **PostgreSQL**.
+
+#### Configuration via `.env`
+1. Copy `.env.example` to `.env`:
+   ```bash
+   cp .env.example .env
+   ```
+2. Edit `.env` with your settings:
+   ```ini
+   DEV_WORKFLOW_DB_TYPE=mysql
+   DEV_WORKFLOW_DB_URL=mysql://user:pass@localhost:3306/db
+   ```
+
+#### Configuration via Environment Variables
+Alternatively, export variables directly:.
 
 | Variable | Description | Default |
 |----------|-------------|---------|
@@ -252,6 +286,33 @@ Add the environment variable in your Windsurf MCP settings:
 ```
 
 
+
+### ✅ Testing
+
+The project uses Node.js native test runner (`node --test`).
+
+```bash
+npm test
+```
+
+This runs:
+- Unit tests for workflow logic
+- Integration tests for `.env` configuration
+- DB Adapter tests (SQLite always; MySQL/Postgres if configured)
+
+#### Testing Database Adapters
+To verify MySQL or PostgreSQL adapters, run tests with the environment variable set:
+
+```bash
+# Test MySQL
+export DEV_WORKFLOW_DB_URL="mysql://root:pass@localhost:3306/test_db"
+node --test tests/db-adapters.test.js
+
+# Test PostgreSQL
+export DEV_WORKFLOW_DB_URL="postgres://postgres:pass@localhost:5432/test_db"
+node --test tests/db-adapters.test.js
+```
+
 ### Scripts
 
 - `npm run build` - Bundle the source into `dist/index.mjs` for distribution

package/db/adapters/mysql.js

@@ -75,6 +75,13 @@ export class MysqlAdapter extends DbAdapter {
         }
     }
 
+    formatDate(date) {
+        // Ensure we have a string in 'YYYY-MM-DD HH:mm:ss' format
+        const d = date ? new Date(date) : new Date();
+        // slice(0, 19) gives YYYY-MM-DDTHH:mm:ss, then replace T with space
+        return d.toISOString().slice(0, 19).replace('T', ' ');
+    }
+
     async insertHistoryEntry(userId, projectPath, entry) {
         await this.connect();
         const normalizedProjectPath = projectPath || '';
@@ -98,7 +105,7 @@ export class MysqlAdapter extends DbAdapter {
             entry.taskDescription,
             entry.taskType,
             entry.commitMessage,
-            entry.timestamp || new Date().toISOString(),
+            this.formatDate(entry.timestamp),
             entry.forced ? 1 : 0,
             entry.forceReason || null,
             entry.dropped ? 1 : 0,
@@ -150,9 +157,9 @@ export class MysqlAdapter extends DbAdapter {
             normalizedProjectPath,
             rows.length,
             JSON.stringify(taskTypes),
-            lastActive,
+            this.formatDate(lastActive),
             JSON.stringify(recentTasks),
-            new Date().toISOString()
+            this.formatDate(new Date())
         ]);
     }
 
@@ -270,7 +277,7 @@ export class MysqlAdapter extends DbAdapter {
             userId,
             normalizedProjectPath,
             JSON.stringify(state),
-            new Date().toISOString()
+            this.formatDate(new Date())
         ]);
     }
 

package/db/migrations/002_create_users_table.sql

@@ -0,0 +1,22 @@
+-- Create users table for authentication
+CREATE TABLE IF NOT EXISTS users (
+  id SERIAL PRIMARY KEY,
+  username VARCHAR(255) UNIQUE NOT NULL,
+  password_hash VARCHAR(255) NOT NULL,
+  email VARCHAR(255),
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  last_login TIMESTAMP
+);
+
+-- Create index on username for faster lookups
+CREATE INDEX IF NOT EXISTS idx_users_username ON users(username);
+
+-- Create sessions table for express-session
+CREATE TABLE IF NOT EXISTS "session" (
+  "sid" varchar NOT NULL COLLATE "default",
+  "sess" json NOT NULL,
+  "expire" timestamp(6) NOT NULL,
+  CONSTRAINT "session_pkey" PRIMARY KEY ("sid")
+);
+
+CREATE INDEX IF NOT EXISTS "IDX_session_expire" ON "session" ("expire");

package/db/migrations/003_create_workflow_history.sql

@@ -0,0 +1,14 @@
+-- Create workflow_history table
+CREATE TABLE IF NOT EXISTS workflow_history (
+  id SERIAL PRIMARY KEY,
+  task_type VARCHAR(50) NOT NULL,
+  description TEXT NOT NULL,
+  commit_message TEXT,
+  completed_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  tests_passed BOOLEAN DEFAULT FALSE,
+  documentation_type VARCHAR(50),
+  user_id INTEGER REFERENCES users(id)
+);
+
+-- Create index on completed_at for faster sorting
+CREATE INDEX IF NOT EXISTS idx_workflow_history_completed_at ON workflow_history(completed_at DESC);

package/db/migrations/004_fix_workflow_history.sql

@@ -0,0 +1,3 @@
+-- Add missing columns for frontend compatibility
+ALTER TABLE workflow_history ADD COLUMN IF NOT EXISTS tests_passed BOOLEAN DEFAULT FALSE;
+ALTER TABLE workflow_history ADD COLUMN IF NOT EXISTS documentation_type VARCHAR(50);

package/docker-compose.yml

@@ -0,0 +1,24 @@
+version: '3.8'
+
+services:
+  postgres:
+    image: postgres:16-alpine
+    container_name: dev-workflow-postgres
+    restart: unless-stopped
+    environment:
+      POSTGRES_USER: devworkflow
+      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-devworkflow_secure_password_change_me}
+      POSTGRES_DB: devworkflow
+    ports:
+      - "5432:5432"
+    volumes:
+      - postgres_data:/var/lib/postgresql/data
+    healthcheck:
+      test: [ "CMD-SHELL", "pg_isready -U devworkflow" ]
+      interval: 10s
+      timeout: 5s
+      retries: 5
+
+volumes:
+  postgres_data:
+    driver: local

package/docs/GCP_DEPLOYMENT.md

@@ -0,0 +1,298 @@
+# Deploying to Google Cloud Platform with Docker
+
+This guide walks you through deploying the dev-workflow MCP server to Google Cloud Compute Engine using Docker and PostgreSQL.
+
+## Prerequisites
+
+- Google Cloud Platform account with a Compute Engine instance running
+- SSH access to your GCP instance
+- Git installed locally and on GCP instance
+- Basic familiarity with Docker and SSH
+
+## Architecture Overview
+
+The deployment consists of two Docker containers:
+- **MCP Server**: Node.js application running the dev-workflow MCP server
+- **PostgreSQL**: Database for persistent workflow state storage
+
+Communication between your local MCP client and the cloud server happens via SSH tunneling.
+
+## Step 1: Prepare Your GCP Instance
+
+### 1.1 SSH into Your Instance
+
+```bash
+ssh your-username@YOUR_GCP_IP
+```
+
+### 1.2 Run the Setup Script
+
+From your local machine, copy the setup script to your GCP instance:
+
+```bash
+scp scripts/setup-gcp-instance.sh your-username@YOUR_GCP_IP:~/
+ssh your-username@YOUR_GCP_IP 'bash ~/setup-gcp-instance.sh'
+```
+
+This script will:
+- Install Docker and Docker Compose
+- Install Git
+- Create the application directory
+
+**Note**: You may need to log out and back in for Docker group permissions to take effect.
+
+## Step 2: Deploy the Application
+
+### 2.1 Clone the Repository
+
+On your GCP instance:
+
+```bash
+cd ~/dev-workflow-mcp-server
+git clone https://github.com/programinglive/dev-workflow-mcp-server.git .
+```
+
+### 2.2 Configure Environment Variables
+
+Create a `.env` file from the production template:
+
+```bash
+cp .env.production .env
+nano .env
+```
+
+Update the following values:
+- `POSTGRES_PASSWORD`: Set a strong, unique password
+- `DEV_WORKFLOW_DB_URL`: Update with the same password
+- `DEV_WORKFLOW_USER_ID`: (Optional) Set your username
+
+Example `.env`:
+```bash
+DEV_WORKFLOW_DB_TYPE=postgres
+DEV_WORKFLOW_DB_URL=postgres://devworkflow:MySecureP@ssw0rd@postgres:5432/devworkflow
+POSTGRES_PASSWORD=MySecureP@ssw0rd
+DEV_WORKFLOW_USER_ID=dhika
+NODE_ENV=production
+```
+
+### 2.3 Start the Containers
+
+```bash
+docker-compose up -d
+```
+
+### 2.4 Verify Deployment
+
+Check that both containers are running:
+
+```bash
+docker-compose ps
+```
+
+You should see:
+```
+NAME                      STATUS
+dev-workflow-mcp          Up
+dev-workflow-postgres     Up (healthy)
+```
+
+View logs:
+```bash
+docker-compose logs -f mcp-server
+```
+
+## Step 3: Configure Local MCP Client
+
+Update your local MCP client configuration to connect via SSH.
+
+### Windows (Claude Desktop)
+
+Edit `C:\Users\DHIKA\.gemini\antigravity\mcp_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "dev-workflow": {
+      "command": "ssh",
+      "args": [
+        "-i", "C:\\Users\\DHIKA\\.ssh\\id_rsa",
+        "your-username@34.50.121.142",
+        "docker", "exec", "-i", "dev-workflow-mcp", "node", "/app/index.js"
+      ]
+    }
+  }
+}
+```
+
+### Linux/Mac
+
+Edit your MCP config file:
+
+```json
+{
+  "mcpServers": {
+    "dev-workflow": {
+      "command": "ssh",
+      "args": [
+        "-i", "/home/user/.ssh/id_rsa",
+        "your-username@34.50.121.142",
+        "docker", "exec", "-i", "dev-workflow-mcp", "node", "/app/index.js"
+      ]
+    }
+  }
+}
+```
+
+**Important**: Replace:
+- `your-username` with your actual GCP username
+- `34.50.121.142` with your actual GCP external IP
+- SSH key path with your actual key location
+
+## Step 4: Test the Connection
+
+### 4.1 Test SSH Connection
+
+From your local machine:
+
+```bash
+ssh your-username@34.50.121.142 'docker exec -i dev-workflow-mcp node /app/index.js call get_workflow_status'
+```
+
+You should see the workflow status output.
+
+### 4.2 Test via MCP Client
+
+Restart your MCP client (e.g., Claude Desktop) and try using a dev-workflow command like `start_task`.
+
+## Updating the Deployment
+
+### Automated Deployment
+
+Use the deployment script from your local machine:
+
+```bash
+# Set environment variables
+export GCP_USER=your-username
+export GCP_HOST=34.50.121.142
+export GCP_SSH_KEY=~/.ssh/id_rsa
+
+# Run deployment
+bash scripts/deploy-gcp.sh
+```
+
+### Manual Update
+
+On your GCP instance:
+
+```bash
+cd ~/dev-workflow-mcp-server
+git pull origin main
+docker-compose down
+docker-compose build --no-cache
+docker-compose up -d
+```
+
+## Database Management
+
+### Backup Database
+
+```bash
+docker exec dev-workflow-postgres pg_dump -U devworkflow devworkflow > backup.sql
+```
+
+### Restore Database
+
+```bash
+cat backup.sql | docker exec -i dev-workflow-postgres psql -U devworkflow devworkflow
+```
+
+### Access PostgreSQL Console
+
+```bash
+docker exec -it dev-workflow-postgres psql -U devworkflow devworkflow
+```
+
+Common commands:
+- `\dt` - List tables
+- `\d table_name` - Describe table
+- `SELECT * FROM workflow_state;` - View workflow data
+
+## Troubleshooting
+
+### Container Won't Start
+
+Check logs:
+```bash
+docker-compose logs mcp-server
+docker-compose logs postgres
+```
+
+### Database Connection Issues
+
+Verify PostgreSQL is healthy:
+```bash
+docker-compose ps
+docker exec dev-workflow-postgres pg_isready -U devworkflow
+```
+
+### SSH Connection Fails
+
+Test basic SSH:
+```bash
+ssh -v your-username@YOUR_GCP_IP
+```
+
+Check SSH key permissions:
+```bash
+chmod 600 ~/.ssh/id_rsa
+```
+
+### MCP Client Can't Connect
+
+1. Verify SSH works: `ssh your-username@YOUR_GCP_IP 'echo test'`
+2. Test Docker exec: `ssh your-username@YOUR_GCP_IP 'docker ps'`
+3. Check MCP server: `ssh your-username@YOUR_GCP_IP 'docker logs dev-workflow-mcp'`
+
+## Security Best Practices
+
+1. **Change Default Passwords**: Always use strong, unique passwords in `.env`
+2. **Firewall Configuration**: Only expose necessary ports (SSH port 22)
+3. **SSH Key Authentication**: Disable password authentication, use SSH keys only
+4. **Regular Updates**: Keep Docker images and system packages updated
+5. **Backup Regularly**: Schedule automated database backups
+
+## Performance Optimization
+
+### Monitor Resource Usage
+
+```bash
+docker stats
+```
+
+### Increase PostgreSQL Performance
+
+Edit `docker-compose.yml` to add PostgreSQL tuning:
+
+```yaml
+postgres:
+  environment:
+    POSTGRES_SHARED_BUFFERS: 256MB
+    POSTGRES_EFFECTIVE_CACHE_SIZE: 1GB
+```
+
+## Uninstalling
+
+To completely remove the deployment:
+
+```bash
+cd ~/dev-workflow-mcp-server
+docker-compose down -v  # -v removes volumes (deletes data!)
+cd ~
+rm -rf dev-workflow-mcp-server
+```
+
+## Support
+
+For issues or questions:
+- GitHub Issues: https://github.com/programinglive/dev-workflow-mcp-server/issues
+- Documentation: https://devworkflow.programinglive.com/

package/docs/product/PRD.md

@@ -4,7 +4,7 @@
 - **Product**: Development Workflow MCP Server
 - **Prepared by**: Cascade (AI assistant)
 - **Date**: 2025-12-16
-- **Status**: Live v1.6+
+- **Status**: Live v1.7.11
 
 ## 2. Problem Statement
 Developers need structured guidance to maintain disciplined workflows across projects. Existing tooling lacks enforcement of sequential best practices (testing, documentation, release hygiene) and offers limited visibility into historical task execution.
@@ -38,6 +38,10 @@ Developers need structured guidance to maintain disciplined workflows across pro
 - Guard release commands to ensure prerequisites are satisfied.
 - Support `run_full_workflow` for scripted execution of all steps with validation.
 - Web dashboard displays version dynamically from `package.json` via `/api/version` endpoint to stay in sync after releases.
+- [x] **Consolidated CI/CD**: Unified release and publish workflows.
+- [x] **Multi-Database Support**: SQLite, MySQL, and PostgreSQL adapters implemented and verified.
+- [x] **Environment Configuration**: `.env` file support added.
+- [x] **Comprehensive Testing**: Automated tests for DB adapters and environment loading.
 - **Multi-Database Support**: Abstract the storage layer to support:
     - SQLite (default/local)
     - MySQL