addtaskmanager

This MCP server implements the ADD (Assess-Decide-Do) framework for the addTaskManager app. It provides realm-based operations to create and manage tasks, projects, ideas, and collections within the Assess realm, assign contexts and due dates in Decide, and mark items as complete in Do, while enforcing read-only constraints where required. The server exposes a set of tools such as assess_create_task, decide_set_task_due_date, do_mark_task_as_done, and various query operations like get_tasks_by_realm and get_tasks_by_context. To use it with Claude Desktop, configure your Claude MCP entry to point at the built server (dist/index.js) and supply CloudKit credentials. From there, you can authenticate a user, then issue tools to create or modify items in Assess, move items between realms, and query for status across realms. For web or native apps, use the provided get_* and moveToRealm style operations to incorporate ADD-compliant workflows into your product.

Prerequisites:

• Node.js (LTS) installed on your machine or server
• npm or yarn
• Access to CloudKit credentials (container ID and API token)

Install from source (recommended during development):

# Clone the repository
git clone https://github.com/dragosroua/addtaskmanager-mcp-server.git
cd addtaskmanager-mcp-server

# Install dependencies
npm install

# Build (TypeScript to dist/)
npm run build

Environment setup for production:

cp .env.example .env
# Edit .env with your CloudKit and security credentials

Run in production:

npm start

Alternatively, use the npm package (globally) once published:

npm install -g @dragosroua/addtaskmanager-mcp-server
# Start the server (example, may vary by packaging)
npm run start

Tips and notes:

• Ensure CLOUDKIT_API_TOKEN is kept secret and not checked into source control.
• The server enforces ADD framework rules per realm; when issuing tools, respect the permitted operations for each realm (Assess, Decide, Do).
• For Claude Desktop integration, update the mcpServers entry with the correct path to dist/index.js and your environment variables.
• If you rotate API tokens or encryption keys, restart the MCP server to pick up changes.
• Use CLOUDKIT_ENVIRONMENT=production for live data; use development for testing against a sandbox CloudKit container.
• Enable RATE_LIMIT, AUDIT_LOGGING, and proper SESSION_TIMEOUT in production to improve security and observability.