Let your assistant tell you when it is done

You ask Claude to run a migration, a build or a long scrape, and then you walk away. Webhooky gives it one ability: send a push notification to your phone. It tells you itself, instead of writing code that tells you. As a hosted server at mcp.webhooky.app, or as a package your own machine runs.

You:    Run the migration and let me know when it's done.
Claude: [runs it, then calls send_notification]
📱      ✅ Migration done · 14,203 rows · 6m12s

First, the endpoint URL

Install the Webhooky app for iOS or Android and copy the endpoint URL. There is no account to create, no API key to generate and no OAuth dance. The URL exists the moment the app opens. The random part at the end is your key, and it is all either server needs.

Then pick a server

There are two, with the same two tools. Remote is hosted at mcp.webhooky.app and needs nothing installed, which is the only option in a client that cannot run a process on your machine: claude.ai in a browser, the Claude app on a phone, ChatGPT. Local is the npm package, run by your client on your own machine, which is the better one when you would rather the key never left it.

Remote: Claude Code

claude mcp add --transport http webhooky https://mcp.webhooky.app \
  --header "Authorization: Bearer YOUR_KEY"

Remote: a client that asks only for a URL

Plenty of connector dialogs have a field for the server address and nowhere to put a header. Then the key goes in the path, and that one URL is the entire configuration:

https://mcp.webhooky.app/YOUR_KEY

As config, for clients that take JSON:

{
  "mcpServers": {
    "webhooky": {
      "type": "http",
      "url": "https://mcp.webhooky.app",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

It keeps nothing between calls: no session, no account, no log of what you sent. The key arrives with the request, turns into the same POST to api.webhooky.app that the local server makes, and is gone when the response is written. It also sits beside the delivery path rather than inside it, so if it is ever down, your webhooks are not.

Local: Claude Code

claude mcp add webhooky \
  -e WEBHOOKY_URL=https://api.webhooky.app/YOUR_KEY \
  -- npx -y webhooky-mcp

Local: Claude Desktop, Cursor, Zed and the rest

{
  "mcpServers": {
    "webhooky": {
      "command": "npx",
      "args": ["-y", "webhooky-mcp"],
      "env": { "WEBHOOKY_URL": "https://api.webhooky.app/YOUR_KEY" }
    }
  }
}

Two tools

send_notification takes a title, and optionally a message, a sound and whether to vibrate. It reports an error, rather than a cheerful success, when a notification was accepted but not delivered, which is what happens when the free monthly quota is used up.

list_sounds returns the 40 sounds grouped by meaning: money, success, failure, informational, attention-grabbing, playful. The assistant picks one that matches the event instead of guessing from an id, so a finished build and a failed one do not sound alike.

Why handing it the URL is safe

The endpoint URL can do exactly one thing: trigger a notification on your phone. It cannot read your history, reach your account or expose any data. Anyone who knows it can send you notifications, and that is the whole blast radius.

Neither server takes it as a tool argument. The local one reads it from the environment, the remote one from the request your client makes, and in both cases a model cannot be talked into sending to a different endpoint: the key never enters the conversation, and it is stripped from error messages before they reach the model. If it ever leaks, delete the endpoint in the app and create a new one. The old URL dies instantly.

Where it lives

Without MCP

If your client does not speak the Model Context Protocol, the endpoint is a plain URL and one POST is the whole integration:

curl -X POST https://api.webhooky.app/YOUR_KEY \
  -H "Content-Type: application/json" \
  -d '{"title": "✅ Build green", "message": "42 tests, 6m12s", "sound": "level_up_2"}'