Cancel a scheduled reminder
Cancels a reminder created via POST /v1/reminders — the cancel_reminder MCP tool’s backing endpoint. Always succeeds for any well-formed id once authorized: the server never stored the reminder (spec D10), so it cannot distinguish an unknown or already-fired id from a real, still-pending one. It forwards the cancel to the owner’s paired phone, which no-ops on anything it doesn’t recognize. There is no 404 for this reason — only a 400 if id isn’t even shaped like an id this server could have minted (rmd_ followed by 32 lowercase hex characters); that is a format check, never an existence check.
Requires a paired phone device on the account behind the bearer token (409 no_phone_device).
Authorizations
Opaque bearer token created on your paired Android phone. The format is rfk_live_ followed by 32 URL-safe alphanumeric characters (≥160 bits of entropy). Test tokens use the rfk_test_ prefix.
Path Parameters
The reminder id returned by POST /v1/reminders.
^rmd_[0-9a-f]{32}$"rmd_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b"
Response
Cancel forwarded to the phone. Does not confirm the reminder existed or was still pending — see the honesty note above.
Always cancel_requested. Fire-and-forget: the phone cancels its local alarm; an unknown or already-fired id is a no-op.
cancel_requested "cancel_requested"