Devpipe MCP Server

# Cleanup Summary: Natural Language Prompting Focus ## Overview Removed debug code and DEVPIPE_CWD workarounds in favor of a simpler approach: users specify project paths directly in their natural language prompts. ## Changes Made ### 1. Code Cleanup **Removed:** - ❌ `DEBUG_MCP` environment variable logging in `src/utils.ts` - ❌ `DEVPIPE_CWD` fallback logic in `findConfigFile()` - ❌ `test-cwd.js` debug script **Simplified:** - ✅ `findConfigFile()` now only uses `startDir` parameter or `process.cwd()` - ✅ Error messages now suggest using explicit paths in prompts instead of environment variables ### 2. Documentation Updates **Updated:** - ✅ `README.md` - Removed `DEVPIPE_CWD` from configuration examples - ✅ `README.md` - Added "How to Prompt" section with clear examples - ✅ `README.md` - Added examples for multi-project workflows - ✅ Error messages - Now suggest natural language prompting **Created:** - ✅ `docs/PROMPTING_GUIDE.md` - Comprehensive guide on how to prompt effectively - ✅ `docs/archive/README.md` - Explanation of archived debug docs **Archived:** - 📦 `docs/DEVPIPE_CWD.md` → `docs/archive/` - 📦 `docs/FIX_SUMMARY.md` → `docs/archive/` - 📦 `docs/TEST_WHAT_DIRECTORY.md` → `docs/archive/` - 📦 `docs/WORKSPACE_CONTEXT_FINDINGS.md` → `docs/archive/` - 📦 `docs/DEBUG_WORKSPACE_CONTEXT.md` → `docs/archive/` - 📦 `docs/INITIALIZE_LOGGING.md` → `docs/archive/` - 📦 `MCP_FIX_COMPLETE.md` → `docs/archive/` - 📦 `QUICK_FIX_GUIDE.md` → `docs/archive/` ## Key Insight **The MCP server doesn't need to know about workspace context or have environment variables set.** Users simply tell the AI which project they want to work with: - "Analyze this project" - "Run devpipe in /Users/you/projects/my-app" - "Show tasks from the devpipe project" The AI assistant translates these natural language requests into the appropriate MCP tool calls with explicit `projectPath` or `config` parameters. ## Configuration Changes ### Before (Complex) ```json { "mcpServers": { "devpipe": { "command": "devpipe-mcp", "env": { "DEVPIPE_CWD": "/path/to/your/project" } } } } ``` ### After (Simple) ```json { "mcpServers": { "devpipe": { "command": "devpipe-mcp" } } } ``` ## User Experience ### Before - Set `DEVPIPE_CWD` for each project - Restart IDE when switching projects - Limited to one project at a time - Complex configuration ### After - No configuration needed - Just specify project in prompts - Work with multiple projects simultaneously - Simple and intuitive ## Example Prompts ``` # Single project "Analyze this project" "Run devpipe" # Multiple projects "Analyze /Users/you/projects/frontend" "Now check /Users/you/projects/backend" # Explicit paths "Run tests in /Users/you/projects/api" "Show tasks from /Users/you/projects/web-app/config.toml" ``` ## Benefits 1. **Simpler codebase** - Removed debug code and workarounds 2. **Easier to use** - No environment variables to configure 3. **More flexible** - Work with multiple projects simultaneously 4. **Better UX** - Natural language is more intuitive 5. **Less maintenance** - Fewer edge cases and configuration issues ## Build Status ✅ Project builds successfully with `npm run build` ✅ All TypeScript compilation passes ✅ No breaking changes to MCP tool interfaces ## Next Steps Users should: 1. Remove `DEVPIPE_CWD` from their MCP configuration (optional, still works but not needed) 2. Read the [Prompting Guide](./docs/PROMPTING_GUIDE.md) 3. Start using natural language prompts with explicit project references ## Migration **For existing users with `DEVPIPE_CWD` set:** - Your configuration will still work - But you can simplify it by removing the `env` section - Start using explicit paths in prompts for better flexibility **For new users:** - Just install and configure the MCP server - No environment variables needed - Use natural language prompts with project paths