Initial commit: CursorFlow MCP Server

Author: yasinboelhouwer

.env.example

@@ -0,0 +1,31 @@
+# Server Configuration
+PORT=3002
+HOST=localhost
+
+# Authentication
+AUTH_TOKEN=your-secret-token
+
+# Data Storage
+DATA_DIR=./data
+MEMORY_BANK_DIR=./data/memory-bank
+WORKFLOWS_DIR=./data/workflows
+MODES_DIR=./data/modes
+
+# Logging
+LOG_LEVEL=info
+
+# Performance
+ENABLE_CACHE=true
+
+# Database (optional)
+USE_DATABASE=false
+DATABASE_PATH=./data/cursorflow.db
+
+# Memory Bank Configuration
+MAX_HISTORY_VERSIONS=10
+
+# Mode Configuration
+MODES_PATH=./.cursor
+
+# Workflow Configuration
+WORKFLOWS_PATH=./workflows 

.eslintrc.js

@@ -0,0 +1,21 @@
+module.exports = {
+  env: {
+    node: true,
+    es2021: true,
+    jest: true,
+  },
+  extends: ['eslint:recommended'],
+  parserOptions: {
+    ecmaVersion: 'latest',
+    sourceType: 'module',
+  },
+  rules: {
+    'no-console': 'off', // Allow console for server logging
+    'no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
+    'semi': ['error', 'always'],
+    'quotes': ['error', 'single'],
+    'indent': ['error', 2],
+    'comma-dangle': ['error', 'always-multiline'],
+    'eol-last': ['error', 'always'],
+  },
+}; 

.github/workflows/ci.yml

@@ -0,0 +1,40 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x]
+
+    steps:
+    - uses: actions/checkout@v3
+    
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+        
+    - name: Install dependencies
+      run: npm ci
+      
+    - name: Create data directories
+      run: |
+        mkdir -p data/memory-bank
+        mkdir -p data/workflows
+        mkdir -p data/modes
+        
+    - name: Run tests
+      run: npm test
+
+    - name: Check for linting errors
+      run: npm run lint
+      if: ${{ always() }} 

.gitignore

@@ -1,5 +1,49 @@
-memory-bank/
+# Dependency directories
+node_modules/
+.npm/
+
+# Runtime data
+logs/
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Environment variables
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# Testing
+coverage/
+temp-test/
+
+# Build outputs
+dist/
+build/
+out/
+
+# IDE/Editor folders
+.idea/
+.vscode/
+*.swp
+*.swo
+.DS_Store
+
+# Project specific
+.cursor/
 dev/
-.vscode
-.roomodes
-.roo/
+
+# Keep data structure but not contents
+data/memory-bank/*
+!data/memory-bank/.gitkeep
+data/workflows/*
+!data/workflows/.gitkeep
+data/modes/*
+!data/modes/.gitkeep

CONTRIBUTING.md

@@ -1,78 +1,76 @@
-# Contributing to RooFlow
+# Contributing to CursorFlow MCP Server
 
-Thank you for your interest in contributing to RooFlow! We welcome contributions from everyone.  This document outlines how to contribute to the project.
+Thank you for considering contributing to the CursorFlow MCP Server! This document provides guidelines and instructions for contributing to this project.
 
-## Ways to Contribute
+## Code of Conduct
 
-*   **Bug Reports:** If you find a bug, please open an issue on the GitHub repository, providing a clear description of the problem, steps to reproduce it, and your expected vs. actual results. Include the Roo version, VS Code version, and operating system.
-*   **Feature Requests:**  If you have an idea for a new feature, open an issue on GitHub and describe the feature, its benefits, and any potential implementation details.
-*   **Code Contributions:**  If you want to contribute code (bug fixes, new features, improvements), please follow these steps:
-    1.  **Fork the Repository:** Create a fork of the RooFlow repository on GitHub.
-    2.  **Create a Branch:** Create a new branch for your changes (e.g., `feature/my-new-feature` or `bugfix/issue-123`). Use descriptive branch names.
-    3.  **Make Changes:** Make your changes, following the coding style and conventions of the project.
-    4.  **Test Thoroughly:**  Ensure your changes work correctly and don't introduce new issues.  Test with and without an existing Memory Bank. Test the UMB command.
-    5.  **Commit Changes:** Commit your changes with clear and descriptive commit messages.
-    6.  **Push to Your Fork:** Push your branch to your forked repository.
-    7.  **Create a Pull Request:** Create a pull request from your branch to the `main` branch of the RooFlow repository.  Clearly describe your changes and the problem they solve or the feature they add.
-*   **Documentation:**  Improvements to the documentation (README, etc.) are also welcome. Follow the same process as for code contributions.
+By participating in this project, you agree to maintain a respectful and inclusive environment for everyone.
 
-## Development Setup
+## How Can I Contribute?
 
-To develop RooFlow, you'll need:
+### Reporting Bugs
 
-1.  **VS Code:**  Install Visual Studio Code.
-2.  **Roo Code Extension:** Install the Roo Code extension from the VS Code Marketplace.
-3.  **Git:**  Install Git for version control.
-4.  **Node.js and npm (likely):** While RooFlow itself doesn't have *code* in the traditional sense, the Roo Code extension likely uses Node.js and npm for its build process.  If you're modifying the `system-prompt-[mode]` files, you *might* need to rebuild the extension.  Check the Roo Code documentation for specific instructions.
+When reporting bugs, please include:
+- A clear and descriptive title
+- Steps to reproduce the issue
+- Expected behavior
+- Actual behavior
+- Screenshots (if applicable)
+- Environment details (OS, Node.js version, etc.)
 
-**Project Structure:**
+### Suggesting Enhancements
 
-The RooFlow project consists of the following files, which you should place in your project's root directory:
+Enhancement suggestions are also welcome. Please include:
+- A clear and descriptive title
+- A detailed description of the proposed enhancement
+- Any potential implementation details (if you have ideas)
+- Why this enhancement would be useful to most users
 
-*   `.clinerules-architect`:  Defines the behavior of Architect mode.
-*   `.clinerules-code`:  Defines the behavior of Code mode.
-*   `.clinerules-debug`:  Defines the behavior of Debug mode.
-*   `.clinerules-ask`:  Defines the behavior of Ask mode.
-*   `.clinerules-test`: Defines the behavior of Test mode.
-*   `.roo/`: A directory containing the system prompts.
-    *   `system-prompt-architect`: System prompt for Architect mode.
-    *   `system-prompt-code`: System prompt for Code mode.
-    *   `system-prompt-debug`: System prompt for Debug mode.
-    *   `system-prompt-ask`: System prompt for Ask mode.
-    *  `system-prompt-test`: System prompt for Test mode.
-*  `.roomodes`: Defines custom modes.
-*   `README.md`:  This file.
-* `projectBrief.md`: Optional project brief.
+### Pull Requests
 
-**Memory Bank:**
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Run tests to ensure they pass (`npm test`)
+5. Commit your changes (`git commit -m 'Add some amazing feature'`)
+6. Push to the branch (`git push origin feature/amazing-feature`)
+7. Open a Pull Request
 
-The `memory-bank/` directory is created automatically by RooFlow.  Do *not* create it manually.
+## Development Setup
 
-**Testing:**
+1. Clone your fork of the repository
+2. Install dependencies: `npm install`
+3. Create your `.env` file based on `.env.example`
+4. Start the server in development mode: `npm run dev`
 
-*   **Test Thoroughly:**  Before submitting any changes, test them thoroughly in various scenarios.
-*   **Memory Bank Presence/Absence:** Test with and without an existing Memory Bank.
-*   **UMB Command:** Test the "Update Memory Bank" (UMB) command to ensure it works correctly.
-*   **Mode Switching:** Test switching between different modes.
-*   **Error Handling:** Test how RooFlow handles errors and unexpected situations.
+## Coding Guidelines
 
-## Coding Style
+- Follow the existing code style
+- Write unit tests for new features
+- Update documentation for any changes to the API or features
+- Keep pull requests focused on a single feature or bug fix
 
-*   **YAML:**  The `.clinerules-[mode]` and `system-prompt-[mode]` files use YAML format.  Use consistent indentation (2 spaces) and follow YAML best practices.
-*   **Markdown:** The Memory Bank files (`.md`) use Markdown format.
-*   **Clarity:**  Write clear, concise, and unambiguous instructions.
-* **Comments**: Use comments within the YAML files to explain complex logic.
+## Commit Messages
 
-## Pull Request Guidelines
+- Use the present tense ("Add feature" not "Added feature")
+- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+- Limit the first line to 72 characters or less
+- Reference issues and pull requests in the commit message
 
-*   **Descriptive Title:** Use a clear and descriptive title for your pull request.
-*   **Detailed Description:**  Provide a detailed description of your changes, including the motivation for the changes, the approach taken, and any relevant context.
-*   **Link to Issue:** If your pull request addresses an existing issue, link to the issue in the description.
-*   **Small, Focused Changes:**  Prefer smaller, focused pull requests over large, monolithic ones.
-*   **Tests:** Include tests for any new functionality or bug fixes.
+## Documentation
 
-## Code of Conduct
+If your changes affect how users interact with the project, please update the README.md file accordingly.
+
+## Testing
+
+Please ensure all tests pass before submitting a pull request:
+
+```bash
+npm test
+```
+
+For new features, please add appropriate tests to ensure functionality.
 
-Please be respectful and constructive in all interactions.
+## License
 
-By contributing to RooFlow, you agree to abide by the terms of the [Apache 2.0 License](LICENSE).
+By contributing to this project, you agree that your contributions will be licensed under the project's [MIT License](LICENSE). 

Dockerfile

@@ -0,0 +1,70 @@
+# CursorFlow MCP Server Dockerfile
+# Multi-stage build for optimized production image
+
+# Build stage
+FROM node:18-alpine AS build
+
+# Set working directory
+WORKDIR /usr/src/app
+
+# Copy package files
+COPY package*.json ./
+
+# Install dependencies
+RUN npm ci --only=production
+
+# Copy source code
+COPY . .
+
+# Create data directories
+RUN mkdir -p /usr/src/app/data/memory-bank
+RUN mkdir -p /usr/src/app/data/workflows
+RUN mkdir -p /usr/src/app/data/modes
+
+# Production stage
+FROM node:18-alpine
+
+# Set environment variables
+ENV NODE_ENV=production
+ENV PORT=3000
+ENV HOST=0.0.0.0
+ENV DATA_DIR=/data
+ENV MEMORY_BANK_DIR=/data/memory-bank
+ENV WORKFLOWS_DIR=/data/workflows
+ENV MODES_DIR=/data/modes
+ENV LOG_LEVEL=info
+
+# Create app directory
+WORKDIR /usr/src/app
+
+# Copy from build stage
+COPY --from=build /usr/src/app/node_modules ./node_modules
+COPY --from=build /usr/src/app/src ./src
+COPY --from=build /usr/src/app/public ./public
+COPY --from=build /usr/src/app/package*.json ./
+
+# Create data directories
+RUN mkdir -p /data/memory-bank
+RUN mkdir -p /data/workflows
+RUN mkdir -p /data/modes
+
+# Add a non-root user
+RUN addgroup -g 1001 -S cursorflow && \
+    adduser -u 1001 -S cursorflow -G cursorflow
+
+# Set ownership
+RUN chown -R cursorflow:cursorflow /usr/src/app
+RUN chown -R cursorflow:cursorflow /data
+
+# Switch to non-root user
+USER cursorflow
+
+# Expose port
+EXPOSE 3000
+
+# Health check
+HEALTHCHECK --interval=30s --timeout=5s --start-period=5s --retries=3 \
+  CMD wget -qO- http://localhost:3000/health || exit 1
+
+# Run the application
+CMD ["node", "src/index.js"]