Lockscreen MCP

Agent-created reminders, rendered into a lockscreen workflow.

Send only the tasks a person still has to do in the real world: medication, documents, errands, appointments, family, travel, or payments. Everything else should stay in normal agent logs.

Open debug console Open generator bridge

MCP tools/call example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "push_lockscreen_reminders",
    "arguments": {
      "reminders": [
        {
          "source": "openclaw",
          "title": "Bring passport before leaving",
          "kind": "document",
          "priority": "high",
          "dueAt": "2026-04-29T18:00:00+08:00",
          "location": "Front door",
          "requiresHuman": true
        }
      ]
    }
  }
}

1. Agent pushes

Use MCP JSON-RPC or the REST endpoint to submit structured reminder events.

2. Queue filters

The active queue keeps only human-required reminders that deserve lockscreen space.

3. Generator renders

Open the generator bridge to turn the active queue into a QR/download wallpaper.

REST endpoint

Production requests should include `Authorization: Bearer` or `x-agent-api-key`. Local development stays open when no agent key is configured and `NODE_ENV` is not production.

curl -X POST https://lockscreentodo.com/api/agent/reminders \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $LOCKSCREEN_AGENT_API_KEY" \
  -d '{
    "reminders": [
      {
        "source": "agent",
        "title": "Take medication after dinner",
        "kind": "medication",
        "priority": "critical",
        "requiresHuman": true
      }
    ]
  }'