gsd-task-manager

This MCP server hosts the GSD Task Manager capabilities as an MCP service, enabling clients to discover and run the GSD Task Manager tooling in a standardized MCP workflow. The server wraps the GSD Task Manager experience (private, local-first task management with an Eisenhower Matrix, offline support, and optional cloud sync) into an MCP-compatible endpoint so you can orchestrate it alongside other MCP services. Use the provided MCP interface to initialize, configure, and interact with the task manager, including operations like creating tasks, updating quadrants, managing subtasks, applying tags, and leveraging analytics or batch actions through the MCP discovery and command surface. The server exposes the core features of GSD: private local storage (IndexedDB in the browser) with optional PocketBase-based cloud sync, task dependencies, recurring tasks, batching, smart search, and a rich UI/UX surface that supports keyboard shortcuts and a command palette.

To use the MCP server capabilities, first start the MCP server process (which in turn hosts or references the GSD Task Manager tooling). Then, via the MCP client tooling, you can list available tasks, create new tasks, assign urgency/importance, set recurrence, manage dependencies, and explore analytics dashboards. If you enable Cloud Sync, you can synchronize across devices using PocketBase with OAuth providers. The toolset also exposes export/import functionality for task JSON backups and provides privacy-first defaults by storing data locally unless you opt into syncing.

Prerequisites:

• Node.js (LTS version) and npm installed on your machine
• Access to a terminal/command prompt

Installation steps:

1. Ensure Node.js and npm are installed

   • node -v
   • npm -v

2. Install and run the MCP server wrapper package (gsd-mcp-server) via npx (as defined in the mcp_config)

   // You can verify the package exists on npm: https://www.npmjs.com/package/gsd-mcp-server

3. Start the MCP server (using the configuration for gsd-task-manager)

   • Run the command defined in mcp_config, e.g.:

     npx -y gsd-mcp-server

4. Optional: configure environment variables if needed for Cloud Sync or auth

   • Example placeholders to set before starting:

     export GSD_SYNC_ENABLED=true export GSD_PB_ENDPOINT=https://your-pocketbase.example.org

5. Access MCP endpoints

   • Once started, use your MCP client tooling to discover and interact with the gsd-task-manager service.

Notes:

• You can also adapt this to a docker, uvx, or node-based setup if your deployment environment requires it. The provided mcp_config uses npx to fetch and run the MCP server package.

Tips and common issues:

• Ensure Node.js version compatibility with gsd-mcp-server; use LTS releases.
• If you encounter network issues when fetching the MCP server via npx, verify network access and npm registry connectivity.
• When enabling Cloud Sync, configure PocketBase endpoints and OAuth providers (Google/GitHub) as required by your deployment.
• If you migrate data or adjust data models, use the Export/Import feature to back up tasks in JSON.
• For offline usage, verify IndexedDB availability in the browser and ensure the MCP client surface can operate without a network connection.
• If you need to customize environment variables, place them in a standard env block before launching the MCP server process.
• The Task Manager supports a wide range of features (quadrants, dependencies, recurrence, tags, subtasks, batch actions, analytics, and a command palette). Explore the UI and command palette (⌘K / Ctrl+K) to access capabilities quickly.