Things MCP Reminder Wrapper

Overview

Use a strict update-first workflow for Things reminder requests. Resolve relative dates in the user's local timezone, check auth/token state before updates, and avoid creating duplicates unless the user explicitly asks for duplicates.

Workflow

1. Resolve local date anchor first.
   • Run date '+%Y-%m-%d %H:%M:%S %Z %z'.
   • Use America/New_York unless the user provides a different timezone.
2. Check Things MCP readiness before mutations.
   • Run things_capabilities.
   • Run things_auth_get_status.
   • If update/delete may be needed, run things_validate_token_config.
3. Normalize scheduling terms to explicit dates.
   • Convert relative terms like today, tomorrow, next Monday into absolute dates.
   • Always confirm with absolute wording in the final output, for example: Monday, March 2, 2026 at 9:30 AM (America/New_York).
4. Search for existing matching tasks before creating new ones.