Push notifications, for your AI agents.
Connect Claude, or any MCP client, and let it reach your phone. Agents send you alerts when long jobs finish, and ask for approval before they do anything irreversible.
// claude_desktop_config.json
{
"mcpServers": {
"pocketalert": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.pocketalert.app/mcp",
"--header", "Authorization: Bearer ${TOKEN}"],
"env": { "TOKEN": "your-api-key" }
}
}
}Give your agent a way to reach you
An agent that can notify you is a different kind of tool. It can run unattended, tell you what happened, and stop to ask when the next step costs something.
The whole API as tools
Ten tools over one endpoint: send messages, read history, list devices and applications, pull delivery stats.
Know when long jobs land
Your agent runs for forty minutes and finishes at 2am. Your phone tells you, instead of you watching a terminal.
Human-in-the-loop approvals
Send two HTTP action buttons and the agent pauses until you tap Approve or Decline — from the lock screen.
Severity levels included
Agents can raise a critical alert that breaks through silent mode and Do Not Disturb when something is actually on fire.
Any MCP client
Standard Model Context Protocol over HTTP. Works with Claude Desktop, Claude Code, and anything you build yourself.
Scoped, revocable access
Authentication is a bearer token. Issue a dedicated API key for the agent and revoke it without touching anything else.
Three steps to your first agent push
Get an API key
Create a dedicated API key on the API Keys page — one you can revoke without disturbing your scripts.
Add the server
Add the server to your MCP client config with the key as a bearer token, then restart the client.
Send a test push
Ask your agent to send you a test notification. Your phone should buzz within a second.
Connect in a minute
One endpoint, one bearer token. Paste the config into your MCP client and restart it.
Endpoint
https://mcp.pocketalert.app/mcpAuthentication is a bearer token — an API key from API Keys. Issue a separate one for each agent so you can revoke it on its own.
Claude Desktop and Claude Code
{
"mcpServers": {
"pocketalert": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.pocketalert.app/mcp",
"--header",
"Authorization: Bearer ${POCKETALERT_API_TOKEN}"
],
"env": {
"POCKETALERT_API_TOKEN": "your-api-key"
}
}
}
}Clients with native HTTP transport
{
"mcpServers": {
"pocketalert": {
"type": "http",
"url": "https://mcp.pocketalert.app/mcp",
"headers": {
"Authorization": "Bearer your-api-key"
}
}
}
}Check it works
Restart the client, then ask it to list its tools. You should see pocketalert with ten tools registered. Ask it to send you a test notification and your phone will buzz a moment later.
For the full tool reference, severity levels, and approval-button setup, see the MCP documentation.
Questions, answered
It is a Model Context Protocol server that exposes PocketAlert as a set of tools an AI agent can call. Once connected, the agent can send push notifications to your phone, read your message history, list devices and applications, and check delivery statistics.
Any MCP-compatible client works, including Claude Desktop, Claude Code, and agents you have built yourself. The server speaks standard MCP over HTTP at mcp.pocketalert.app/mcp.
With a bearer token. Create an API key on the API Keys page and pass it as Authorization: Bearer <your-api-key>. We recommend issuing a separate key for each agent so you can revoke one without affecting your other integrations.
Ten tools: create_message, create_message_with_attachment, delete_message, list_messages, get_message, get_message_stats, list_devices, get_device, list_applications and get_application.
Yes. create_message accepts action buttons, so an agent can send two HTTP buttons labelled Approve and Decline before doing anything irreversible. You tap one from the lock screen and the request goes straight from your phone to your endpoint.
The agent can only do what the tools allow: send, read and delete your own messages. It cannot change your plan, read your password, or touch other accounts. Give it a dedicated API key and revoking access is a single click.
Your agent just got a notification channel
Add one server to your MCP client and your agent can reach your phone — for finished jobs, for failures, and for the approvals it needs from you.