Send in-app notifications from Claude Desktop

Setup

You need a secret key (nv_live_…) from Dashboard → API keys.

{
  "mcpServers": {
    "nordva": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.nordva.dev",
        "--header",
        "Authorization:${NORDVA_AUTH}"
      ],
      "env": {
        "NORDVA_AUTH": "Bearer nv_live_..."
      }
    }
  }
}

Then ask Claude Desktop

• Notify user 4812 that their import finished, with a link to /imports/77.
• Tell everyone about tonight's planned downtime, 22:00 to 22:30 UTC.
• How many people read last week's broadcast?
• Set up identity verification for the notifications bell.

For “Notify user 4812 that their import finished, with a link to /imports/77.” Claude Desktop calls send_notification with:

{
  "user_id": "4812",
  "title": "Import finished",
  "body": "1,204 rows imported, 3 skipped.",
  "action_url": "/imports/77"
}

Returned: The notification id, the user id, the time it was created and this month's usage against the cap. The user's bell shows it the next time it checks.

Notifications tools and arguments

Behaviour worth knowing

• Every plan can send notifications, capped per project per calendar month: Free 1,000, Indie 20,000, Builder 200,000. A broadcast counts once.
• send_notification reaches real people, so the server marks it destructive and clients ask before calling it. With audience "all" it is one broadcast that shows in every signed-in user's bell for 30 days.
• list_notifications shows, for a broadcast, how many people it reached (their bell checked after it was sent) and how many read it.
• Your pages read the bell with the publishable key, the user's id and a user_hash your server computes with the signing secret, so one browser cannot read another user's notifications.
• create_notifications_signing_secret and rotate_notifications_signing_secret return the secret once, in the text only; the agent is told to write it to your server's env file and never to the browser.
• publish_changelog_entry with notify_in_app posts the entry to the bell once when it publishes.
• Notifications older than 90 days are pruned.
• The Connectors screen in Claude Desktop and claude.ai expects OAuth. The Nordva Launch server authenticates with an API key header instead, which is why the bridge is needed there.