HERE MCP send-notification tool
send-notification sends the user a desktop notification through the HERE notification service.
| Tool | Purpose |
|---|---|
send-notification | Send a desktop notification to a user or group |
New to the MCP server? Start with the overview.
What it does
Use send-notification when your agent needs to get the user's attention rather than open an app. For example, an agent that watches market moves, compliance logs, or IT alerts can use it to flag something on the user's desktop.
These notifications go through the same HERE notification service as any other server-side notification, and users see them in the usual HERE notification experience. For details on titles, bodies, and templates, see Get started with notifications.
Security model
- Notifications go through your organization's authenticated HERE notification service.
- Who can receive a notification depends on your organization's notification and identity setup. Limit notifications to the authenticated user unless your integration is designed to target additional recipients.
- Entitlements and access policies still apply. Your agent can't use this tool to bypass notification or identity controls.
Prerequisites
- You can connect to the MCP server. See Connecting for the endpoint and authentication. Then call
tools/listto check thatsend-notificationis available and see its current input schema. - The notification service is available for your HERE organization.
- Your notifications are clear. Keep the title and body short and specific, so the user knows what to do next.
Example
const result = await mcp.call("send-notification", {
title: "Price alert",
body: "AAPL moved more than 2% in the last 15 minutes."
});
Limits
- Notifications only. This tool doesn't raise FDC3 intents or open apps. To open or focus an app, use
raise-intent. - Volume should be limited. Your agent can send notifications much faster than users can read them. Limit the number of notifications you send per user session.
- Not a replacement for in-app workflows. If the user should keep working in a specific app with context filled in, use an intent instead.
Related tools
- HERE MCP server overview
- App and supertab tools: open apps and supertabs, and work with color channels
- HERE MCP intent tools:
list-intent-handlersandraise-intent get-browser-context: read text and markdown from the user's open views