task-orchestrator

Persistent AI memory for coding assistants - MCP server providing context persistence across sessions for Claude, Cursor, Windsurf. MCP Tools for task tracking, workflow automation, and AI memory. Eliminates context loss between sessions.

[{"step":"Initialize the MCP server in your development environment (VS Code with Cursor/Windsurf or Claude with MCP support). Ensure the task orchestrator plugin is installed and configured with your project's repository path.","tip":"Use the MCP inspector tool to verify the server is running before proceeding. Check logs for any initialization errors."},{"step":"Load your project context into the orchestrator using the 'sync_project' command. This will scan your repository for existing tasks, issues, or TODO comments and populate the persistent memory.","tip":"For large projects, run this during a low-activity period. The sync may take several minutes depending on repository size."},{"step":"Use the 'update_task' command to modify task statuses as you work. Include specific details about progress, blockers, or completion. Reference task IDs or descriptions for updates.","tip":"Be consistent with task naming conventions. Use the same identifiers across sessions to maintain continuity."},{"step":"Query the task status regularly using 'get_status' or 'list_tasks' commands. Filter by priority or status to focus on critical items.","tip":"Set up periodic reminders (e.g., every 2 hours) to update task statuses, especially for long-running tasks."},{"step":"Export the task state before ending your session using 'export_state' to ensure all context is preserved for the next session.","tip":"Store exported states in a dedicated directory within your project (e.g., `.mcp/tasks/`). Version control these exports for historical tracking."}]