three.ws Notifications — Claude Code MCP server: inbox and delivery
Hands an agent the three.ws notification inbox: read events, mark them read, tune delivery channels, register Web Push devices.
claude mcp add --env THREE_WS_API_KEY=<THREE_WS_API_KEY> --env THREE_WS_BASE=<THREE_WS_BASE> --env THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> --transport stdio notifications-mcp -- npx -y @three-ws/notifications-mcpWhat three.ws Notifications does
Seven tools over stdio, all scoped to one three.ws account. The agent pulls the inbound feed — market alerts, sales and earnings, purchase receipts, social mentions, IRL interactions, security notices — marks entries read, and deletes the ones it no longer needs. A separate pair of tools covers the delivery matrix: which channels (in_app, push, email, telegram) carry each event category to the owner. Two more register and drop Web Push devices from a browser PushSubscription.
Every call goes to the live three.ws API. The server authenticates with THREE_WS_API_KEY or an OAuth token, sends it as Bearer, and resolves the owning account per request. Nothing is signed locally and no other secret is kept. You need Node 20+ and a key; without the key the server cannot authenticate. Two runtime dependencies: @modelcontextprotocol/sdk and zod.
Deleting a notification and unregistering a device carry destructive annotations, so clients that honour tool annotations will ask before running them. Marking read and patching preferences are idempotent — a repeat call changes nothing.
What it helps with
- catch up on what landed in the inbox since the last check
- clear every unread notification in one call
- stop email delivery for social mentions
- register a browser as a Web Push device
- drop a notification from the feed for good
Example prompts for the agent
- Show my delivery preferences and disable telegram for sales notifications.
- Register this Web Push device and unregister the old one.
How to install three.ws Notifications
Platform CLI
claude mcp add --env THREE_WS_API_KEY=<THREE_WS_API_KEY> --env THREE_WS_BASE=<THREE_WS_BASE> --env THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> --transport stdio notifications-mcp -- npx -y @three-ws/notifications-mcpReplace <…> with your own values
Platform CLI
codex mcp add notifications-mcp --env THREE_WS_API_KEY=<THREE_WS_API_KEY> --env THREE_WS_BASE=<THREE_WS_BASE> --env THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> -- npx -y @three-ws/notifications-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"notifications-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/notifications-mcp"
],
"env": {
"THREE_WS_API_KEY": "<THREE_WS_API_KEY>",
"THREE_WS_BASE": "<THREE_WS_BASE>",
"THREE_WS_TIMEOUT_MS": "<THREE_WS_TIMEOUT_MS>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"notifications-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/notifications-mcp"
],
"env": {
"THREE_WS_API_KEY": "<THREE_WS_API_KEY>",
"THREE_WS_BASE": "<THREE_WS_BASE>",
"THREE_WS_TIMEOUT_MS": "<THREE_WS_TIMEOUT_MS>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e THREE_WS_API_KEY=<THREE_WS_API_KEY> -e THREE_WS_BASE=<THREE_WS_BASE> -e THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> notifications-mcp npx -y @three-ws/notifications-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about three.ws Notifications
How do I install three.ws Notifications in Claude Code?
Run claude mcp add notifications-mcp -e THREE_WS_API_KEY=<THREE_WS_API_KEY> -- npx -y @three-ws/notifications-mcp, replacing the placeholder with your own key.
What does three.ws Notifications do?
It exposes the three.ws notification inbox and delivery controls to an agent: reading events, marking them read, deleting, setting per-category channels, and managing Web Push devices.
What does the server need to run?
Node 20+ and a THREE_WS_API_KEY. The server sends it as a Bearer credential and uses it to resolve the account. Its two runtime dependencies are @modelcontextprotocol/sdk and zod.
