three.ws Notifications MCP Server

ws notification inbox, delivery preferences, and Web Push devices - from any AI agent. Its 7 documented tools cover preferences, push, device.

People who work with preferences, push and device and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

One of 37 MCP servers published from nirholas/three.ws. Stars and repository activity are shared across all of them. See all 37 →

VERIFIED ACTIVE

LAST COMMIT 2026-09-18 · VERIFIED 2026-09-18

Apache-2.0 · JavaScript servers · how we verify → /methodology

01 · Install three.ws Notifications

before you install - you'll need

THREE_WS_API_KEY

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add nirholas-three.ws-packages-notifications -- npx -y @three-ws/notifications-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "nirholas-three.ws-packages-notifications": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/notifications-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license Apache-2.0 - declared in the repository

npm package @three-ws/notifications-mcp - the @three-ws scope differs from the repo owner (nirholas); confirm it's the project's official package

registry namespace io.github.nirholas is GitHub-verified and matches the repo owner

03 · What three.ws Notifications can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

An agent gets 7 documented tools spanning preferences, push, device, including list_notifications, mark_read, delete_notification, get_preferences.

Capability map

Tools grouped from the project's README - what three.ws Notifications lets an agent do.

read & search

2 tools - e.g. Read the account's inbox - the inbound-event feed the platform delivers: market/pump alerts, sales & earnings, purchase receipts, social mentions, IRL interacti; Read the resolved delivery matrix - for…

list_notifications · get_preferences

Mark

1 tool - e.g. Mark notifications read. Wraps POST /api/notifications/:id/read (one) and POST /api/notifications/read-all (all). Pass exactly one of the two arguments. Marking

mark_read

delete

1 tool - e.g. Permanently remove one notification. Wraps DELETE /api/notifications/:id. Irreversible - prefer mark_read for normal triage. Only a notification the caller owns

delete_notification

update

1 tool - e.g. Patch the delivery matrix. Wraps PUT /api/notifications/preferences. Provide at least one of the two arguments. Only the category/channel pairs you pass change;

set_preferences

1 tool - e.g. Register a Web Push device so the account receives push notifications on it. Wraps POST /api/push/subscribe. The subscription argument is exactly what the brows

register_push_device

Unregister

1 tool - e.g. Remove a Web Push device so it stops receiving pushes. Wraps DELETE /api/push/subscribe. Provide at least one of the two arguments - the endpoint is what locate

unregister_push_device

Latest releases

v1.0.0 · 2026-08-28

!three.ws · three.ws is an Android app. Install it and the platform opens full-screen, with no browser chrome around it, and every signature is routed to the wallet on your phone. · Install · 1. Open…

04 · Who maintains three.ws Notifications

three.ws Notifications is maintained by nirholas. We track 66 MCP servers from nirholas - 65 actively maintained, 7,838 combined GitHub stars, oldest repo from Feb 2024. Full record: all servers from nirholas.

05 · Facts

repository: github.com/nirholas/three.ws
website: https://three.ws/
category: AI & ML - actively maintained as of 2026-09-18.
registry: io.github.nirholas/notifications-mcp (active, first published 2026-06-24 · 3 versions)
packages: npm:@three-ws/notifications-mcp

06 · three.ws Notifications FAQ

Is three.ws Notifications still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-18. We re-verify nightly.

What can three.ws Notifications do?

An agent gets 7 documented tools spanning preferences, push, device, including list_notifications, mark_read, delete_notification, get_preferences.

How do I install three.ws Notifications?

Run `npx -y @three-ws/notifications-mcp`. The README documents one environment variable (THREE_WS_API_KEY) to set first. You can also paste the ready-made client config above.

Does three.ws Notifications run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to three.ws Notifications

Alternatives to three.ws Notifications

Maintained AI & ML servers if three.ws Notifications isn't the fit.

Pairs well with

Servers that cover what three.ws Notifications doesn't - only shown when the pairing reason fits the companion.

More AI & ML MCP servers · three.ws Portfolio · three.ws Provenance · pump.fun Solana Data · three.ws Scenes · three.ws Signals