Notify

Open Notify →

Calling it

This is your own data, so a call has to say who you are. Make a token at /token and send it as a header.

curl -H "Authorization: Bearer $MU_TOKEN" \
  https://micro.mu/api/v1/notify/devices

The same method over MCP, which is what an agent speaks: notify_devices. The answer is identical.

How every call behaves →

Methods

GET /api/v1/notify/devices

Whether this account can be reached by notification at all, and on which devices. Worth asking before promising to tell somebody something

Needs an account.

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://micro.mu/api/v1/notify/devices"
POST /api/v1/notify/send

Interrupt yourself on your own devices — a phone, a laptop — with the page closed. For the thing that cannot wait until the next time somebody looks. An answer to a question belongs in the thread it was asked in, not here

Needs an account. Changes something, so POST only.

ArgumentTypeDescription
title *stringThe line on the lock screen. Short — this is the whole message on a watch
bodystringA second line, up to about 300 characters. Optional
urlstringWhere tapping it goes, e.g. /inbox. A notification you cannot act on trains someone to ignore the next one
curl -X POST \
  -H "Authorization: Bearer $MU_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title":"title"}' \
  https://micro.mu/api/v1/notify/send

The same methods are tools over MCP, and every service on this instance is in one reference.