Mobius API

You can manage my reminders through Mobius, a personal assistant that messages me on WhatsApp. Anything you schedule here reaches my phone.

API base URL: https://api.askmobius.com
Auth header on every request: Authorization: Bearer PASTE_YOUR_MOBIUS_API_KEY_HERE

The key identifies me, so never send a chatId — you only ever see my own data. Never print the key back to me or write it into a file you create.

SETUP — DO THIS FIRST IF YOU CAN INSTALL MCP SERVERS

If you support the Model Context Protocol (Claude Code, Cursor, Windsurf, Claude Desktop, and similar), don't just call these endpoints in this one conversation — install them once as a permanent MCP server so they are available in every future session and project:

1. Write a small stdio MCP server that wraps the four endpoints below as tools named
   mobius_create_reminder, mobius_list_reminders, mobius_reschedule_reminder, mobius_cancel_reminder.
   Any MCP SDK is fine; the server is a thin HTTP client, no state of its own.
2. Read the key from an environment variable (MOBIUS_API_KEY) that you set in the server's
   registration config. Do not hardcode it in the server source, and do not write it into a
   file that could be committed to git.
3. Register it at USER / GLOBAL scope, not project scope, so it follows me everywhere.
   Use your own client's mechanism for this — for Claude Code that is
   `claude mcp add --scope user`; other clients have their own config file or command.
   If you are unsure which scope flag your client uses, check its documentation rather
   than guessing, and tell me what you registered and where.
4. Verify it by calling mobius_list_reminders once, then tell me it is installed.

If you cannot install MCP servers, skip all of that and just call the HTTP endpoints directly.

ENDPOINTS

1) Create a reminder — POST /api/reminders (Content-Type: application/json)
   One-off:
     { "task": "call the plumber", "datetime": "2026-08-03T18:00", "tz": "Asia/Kolkata" }
   Recurring:
     { "task": "take meds", "recurring": true, "rrule": "FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=7;BYMINUTE=0", "tz": "Asia/Kolkata" }
   Fields: task (required), datetime (one-off, local wall-clock "YYYY-MM-DDTHH:mm", NO timezone offset, must be in the future),
   recurring + rrule (iCal RFC 5545; put the time of day in BYHOUR/BYMINUTE — there is no separate time field),
   tz (IANA name; defaults to Asia/Kolkata).
   Returns 201 with { id, task, nextFireAt, localTime, rrule, tz, status }.

2) List my reminders — GET /api/reminders
   Pending only by default; add ?all=true for done/cancelled/failed too.

3) Reschedule or rename — PATCH /api/reminders/:id
   { "task": "...", "datetime": "...", "rrule": "...", "tz": "..." } — send only what changes.

4) Cancel — DELETE /api/reminders/:id  →  { "cancelled": true }

RULES
- Resolve relative times ("tomorrow 6pm", "in 30 minutes") into an absolute datetime yourself, in my timezone, and check it is in the future.
- Use the id from create/list for PATCH and DELETE. An id that isn't mine returns 404.
- Errors: 400 = bad payload (the message says what), 401 = bad or revoked key, 404 = no such reminder of mine, 429 = rate limited (30 creates/minute) or I am at my 100 pending-reminder cap.
- After scheduling, confirm back to me using localTime from the response, not the UTC timestamp.

Good uses: ping me when a long build or deploy finishes, remind me to review a PR, or set recurring nudges I asked for in passing.