AlwaysNotify MCP

Connect Claude to your household alerts

AlwaysNotify exposes a secure remote Model Context Protocol (MCP) server. Add one URL, sign in with OAuth, and Claude can help with alerts and reminders using your existing household permissions.

Sign in to AlwaysNotify

MCP server URL

https://app.alwaysnotify.com/api/mcp

This is the resource URL to paste into Claude. Never add an Authorization header or personal token—Claude starts the OAuth flow automatically when the server responds.

Claude web and Claude Desktop

  1. Open Claude settings and choose Connectors.
  2. Add a custom connector and paste the MCP server URL above.
  3. Choose Connect. AuthKit opens so you can sign in, select your household, and approve access.
  4. Return to Claude and enable the AlwaysNotify tools you want to use.

On Team and Enterprise plans, an organization owner may need to add the custom connector before members can connect it.

Claude Code

Add the recommended remote HTTP server from a terminal:

claude mcp add --transport http alwaysnotify https://app.alwaysnotify.com/api/mcp

Then start the OAuth flow:

claude mcp login alwaysnotify

You can also open /mcp inside an interactive Claude Code session and authenticate AlwaysNotify there.

Available AlwaysNotify tools

  • List alerts that still need attention.
  • Search recent alert history.
  • Acknowledge, resolve, or snooze an alert, and record auto-triage corrections such as “too urgent” or “wrong audience.”
  • Create, rename, reorder, or delete shared reminder lists, with the same full-list and permission checks as the dashboard.
  • Create, update, complete, snooze, or cancel one-time reminders and TODOs, including optional list, assignee, and self or household audience.
  • Create daily, weekly, monthly, or yearly series with create_reminder_series, then list them, skip the next occurrence, or cancel the series.
  • Set or clear a custom escalation ladder on an individual reminder occurrence.
  • Paste email, calendar-event, or message text and ask Claude to create a TODO with create_reminder. Assignment marks work ownership and does not change who the reminder pages.

Tool calls use the same membership and permission checks as the AlwaysNotify app. The model cannot choose a different household or grant itself broader access. MCP does not add a separate source-reading tool; paste the source text you want saved as a TODO. It also does not expose Settings, connection OAuth, or rule authoring—use the dashboard for “ignore next time” and other rule changes.

Security and privacy

OAuth access tokens are issued by WorkOS AuthKit for this exact MCP resource. Each request is mapped back to your current WorkOS user and active household membership before a tool runs. If membership is removed, access fails closed.

Review Claude's connector permissions before approving access. Disconnect the connector in Claude settings whenever you no longer want Claude to use AlwaysNotify.

Frequently asked questions

Do I need to mint or copy an API token?

No. AlwaysNotify uses the standard MCP OAuth flow. Claude discovers AuthKit, opens a secure sign-in and consent screen, and manages short-lived access credentials for you.

What can Claude do after I connect AlwaysNotify?

Claude can manage visible alerts and triage corrections; create and organize reminder lists and TODOs; create, skip, or cancel recurring series; and set a reminder-specific escalation ladder. Every action is limited to your active household membership and permissions.

Can I disconnect Claude later?

Yes. Remove or disconnect the AlwaysNotify connector in Claude settings. You can reconnect later through the same OAuth flow.

Does Claude receive my AlwaysNotify password?

No. Authentication happens with WorkOS AuthKit. Claude receives an audience-bound OAuth access token, never your password or an AlwaysNotify session cookie.

← AlwaysNotify home