webhooky-mcp
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
webhooky-mcp
Gives an AI assistant one ability: send a push notification to your phone. Useful when you ask it to do something long-running and then walk away, it can tell you itself instead of writing code that tells you.
You: Run the migration and let me know when it's done.
Claude: [runs it, then calls send_notification]
📱 ✅ Migration done · 14,203 rows · 6m12sSetup
Install the Webhooky app (iOS · Android), create an endpoint and copy its URL. No account needed, the URL exists the moment the app opens. The free plan covers 100 notifications per month across up to 3 endpoints.
There are two ways to run it. The hosted server needs nothing installed and works in clients that cannot start a local process, such as claude.ai in a browser, the Claude app on a phone, or ChatGPT. The npm package below runs on your own machine and keeps the key out of any request to us beyond the notification itself.
Related MCP server: BotBell MCP Server
Hosted, nothing to install
https://mcp.webhooky.app, streamable HTTP. The endpoint key goes in an
Authorization header:
claude mcp add --transport http webhooky https://mcp.webhooky.app \
--header "Authorization: Bearer YOUR_KEY"Clients that only offer a URL field take the key in the path instead:
https://mcp.webhooky.app/YOUR_KEYThe hosted server is stateless. It keeps nothing between calls, and it holds no copy of your key: the key arrives with each request and is used to deliver that one notification.
Local
Claude Code
claude mcp add webhooky -e WEBHOOKY_URL=https://api.webhooky.app/YOUR_KEY -- npx -y webhooky-mcpClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"webhooky": {
"command": "npx",
"args": ["-y", "webhooky-mcp"],
"env": { "WEBHOOKY_URL": "https://api.webhooky.app/YOUR_KEY" }
}
}
}Cursor, Zed and other MCP clients
Same shape: command npx, args ["-y", "webhooky-mcp"], and WEBHOOKY_URL in
the environment.
Tools
send_notification
Argument | Type | Required | Notes |
| string | yes | Max 100 characters |
| string | no | Max 500 characters. Omit to use the endpoint's configured text |
| enum | no | One of the 40 sound ids. Omit to use the endpoint's sound |
| boolean | no | Overrides the endpoint's vibration setting |
Returns a confirmation including how many devices it reached. It reports an error, rather than a cheerful success, when the notification was accepted but not delivered, which is what happens when the free plan's monthly quota is used up. Webhooky answers HTTP 200 in that case on purpose, so that senders like Stripe don't retry, and this server unpacks that distinction for you.
list_sounds
The 40 sounds grouped by meaning (money, success, failure, informational, attention-grabbing, playful), so the assistant can pick one that matches the event instead of guessing from an id.
Configuration
Variable | Required | Default | Notes |
| yes | (none) | Your full endpoint URL, key included |
| no |
| Request timeout |
WEBHOOKY_URL must be https, except on localhost / 127.0.0.1, where plain
http is allowed because nothing leaves the machine.
The server starts and lists its tools even with nothing configured, so a client
can show you what it does before you set anything up. It complains when
send_notification is actually called, and tells you what to set.
A note on your URL
Your 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. The npm package therefore takes it only from the environment, never as a tool argument: a model can't be talked into sending to a different endpoint, and the key never enters the conversation. It is also stripped from any error message before it is returned.
Treat WEBHOOKY_URL the way you would a Slack incoming webhook URL: keep it out
of public repositories, but it is not a password. If it leaks, delete the endpoint in the app and create a new one. The old URL
dies instantly.
Development
npm install
npm test # drives the server over real stdio against a stub endpointLinks
MIT · Aigner Software e.U.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Reach your own phone from an AI agent: notifications, approval questions, reminders, ring, files.
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Send, search, and manage notifications, accounts, and push preferences
Push notifications with personalized sounds - manage and trigger your vybits via MCP
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to send push notifications through the kweenkl service. Allows users to receive contextual notifications from their AI when tasks are complete or important events occur.14 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.29 npm1MIT
- FlicenseAqualityDmaintenanceEnables AI to send push notifications to your phone via a configurable gateway. It is a thin wrapper that posts to an Apprise push gateway.1-
- AlicenseNot gradedqualityBmaintenanceEnables sending push notifications to phones and other devices from any MCP client, with tools for validating users, listing sounds, checking limits, and managing emergency receipts.MIT