Notifications over MCP

idapt's notification action lets an MCP client alert your workspace from outside idapt. Any client whose API key carries the notifications scope can send one 🔔

Send a notification

Call the idapt tool with the notification send action and put the fields in args:

{
  "action": "notification send",
  "args": {
    "workspace": "/owner/my-workspace",
    "target": "all_members",
    "title": "New report",
    "message": "See Q3 in the shared folder.",
    "deepLink": { "kind": "file", "fileId": "FILE_ID" }
  }
}

Required fields

workspace: the workspace-qualified handle ( /owner/workspace-slug). MCP has no chat context, so name it explicitly.
target or recipientIds: set target to all_members, admins, or owner, or pass recipientIds(up to 1000 ids). The two are mutually exclusive.
title(1-120 chars) and message(1-500 chars).

Optional deep link

Pass a deepLink so recipients land on the right resource when they click. It resolves the same way in-app, in email, and in web push. There are 11 kinds:

chat(with an optional messageId), file, workspace, agent, computer, settings, billing, usage, support-ticket, hub, and home.

Pass dedupKey to collapse repeat sends of the same alert within 24 hours per recipient.

Limits and safety

The caller must be a member of the target workspace. Cross-workspace sends are rejected.
Channels intersect with each recipient's preferences. A send cannot override opt-outs or quiet hours.
A human must be attributable, so fully autonomous principals cannot send.
Up to 100 sends per 24 hours per principal. A broadcast to many recipients counts as one send.

Inbox and enumeration

The same key can also read your own inbox. Each row below is an action string you pass to the idapt tool as action:

Command	What it does
`idapt notification list`	List notifications.
`idapt notification preferences`	Get notification preferences.
`idapt notification update-preferences`	Bulk update notification preferences.
`idapt notification config`	Get notification config (toasts, sound, quiet hours).
`idapt notification update-config`	Update notification config.
`idapt notification get`	Get a notification.
`idapt notification send`	Send a notification.
`idapt notification update`	Update a notification (mark read, …).
`idapt notification delete`	Delete a notification.
`idapt notification read-all`	Mark all notifications read.

To notify on a schedule, pair this with an automation whose action is an agent run that sends the notification. See automations and webhooks.

Connecting a client and minting a scoped key are covered in Connect your tool. Use the notifications scope on the key.

What an MCP client can do

The one idapt tool, how to call it, how to discover every action from inside your client, and what is off limits.

MCP permissions

API key scopes, what each one grants, and how to pick the narrowest set for your workflow.

Notifications

Your inbox, delivery channels, quiet hours, and how agents and the API notify you.

Notifications API

Send notifications to workspace members and manage your inbox programmatically.

Was this helpful?