Get a Phone Notification When Perplexity Finishes Deep Research

You hit Enter on a Deep Research query, Perplexity says it's working through sources, and now you've got two options: watch the progress list crawl for a few minutes, or tab away and forget the whole thing exists until tonight. Most of us manage both in the same afternoon.

Deep Research earns the wait: it reads dozens of sources and hands you a cited report you'd have spent an hour assembling by hand. The problem is the wait's shape: a few minutes is too long to stare at a progress list and too short to start anything real. So you alt-tab into Slack "just for a sec," and by the time you resurface, the report's been sitting there for half an hour.

The fix is small: Perplexity supports custom MCP connectors, and TheNotificationApp runs a remote MCP server that pushes straight to your iPhone. Connect the two once, and every research prompt can end with "then ping my phone." Report done, phone buzzes, you walk back. Here's the five-minute setup.

Step 1: Add the MCP connector to Perplexity

Perplexity takes remote MCP servers straight from its settings: nothing to install, no helper process, no JSON file on your machine.

1. Open Settings → Connectors in Perplexity.
2. Click Add connector and pick the custom Remote option.
3. Name it something you'll recognize, thenotification.app works.
4. Set the server URL to https://thenotification.app/mcp.
5. Choose OAuth for authentication and leave any client ID or secret fields blank: the server registers itself.
6. Hit Connect and sign in with your Apple ID.

That Apple sign-in is the entire credential exchange. There's no key to generate, paste, or accidentally screenshot, you get short-lived tokens tied to your Apple ID instead of a permanent secret sitting in a settings page. The MCP docs walk through the same flow for Claude and Cursor if Perplexity isn't your only client.

One prerequisite people skip: install the free TheNotificationApp iOS app and sign in with the same Apple ID. The push needs a registered device to land on: no app on your phone, no buzz in your pocket.

Step 2: End your research prompt with the ping

No automation rules, no config. You ask for the notification in the same prompt that starts the research:

Run deep research on the current state of solid-state battery manufacturing: key players, production capacity, cost-per-kWh trends. When the report is ready, use the notification tool to ping my phone: title "Research done", body = your single most surprising finding.

Perplexity treats the ping as the last step of the job: finish the report, then call the tool with your title and body. That body line is worth stealing: a notification that reads "Semi-solid cells are already shipping at scale" tells you whether to walk back to your desk now or after lunch. "Done" tells you nothing.

Step 3: Send a test, and what to check when it's silent

Before you trust this with a real run, type: "Send a test notification to my phone." Your phone should buzz inside a couple of seconds. If it doesn't, it's almost always one of these:

• No registered device. The iOS app isn't installed, or it's signed in with a different Apple ID than the connector.
• Expired session. The OAuth tokens are short-lived by design; hit Connect again under Settings → Connectors.
• Quota's gone. The API returns a limit error once you've used up your plan, more on that below.

And if a research run ever finishes without a ping (the model got absorbed in its report and forgot, it happens), reply "notify me now." Same tool, one message later.

The same ping, from anything else that finishes

Under the hood, the MCP server calls the same HTTP endpoint you can hit from any script, server, or cron job. One POST:

curl -X POST https://thenotification.app/api/sendNotification \
  -H "app_key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title": "Research done", "body": "The solid-state battery report is ready."}'

The direct API does use an app key. You create one in the dashboard at thenotification.app and drop it in the app_key header. A success comes back as JSON with the device count, and the API reference lists every field and status code. If "ping me when the slow thing finishes" is your whole use case, the pattern generalizes. A Deep Research run is just a long-running script you don't get to watch.

Real talk

Fair warning on the free tier: it's 100 notifications total, not per month. One ping per research run means that lasts a good while, but if you also wire up Claude, Cursor, and three cron jobs to the same account, you'll drain it faster than you'd think. Pro is $2.99/month for 1,000 notifications a month. The other honest note: a Deep Research run takes minutes, not hours. If you genuinely sit and watch it, you don't need this. The ping earns its keep the moment you kick off a query and leave: for lunch, a meeting, or the next task.

Stop checking the tab

Connect the server, send one test, add one sentence to your research prompts. From then on Perplexity works while you do, and your phone tells you when it's your turn again. Worth a look if you're tired of checking whether the robot has finished reading the internet. Grab it free before your next run.

New to this? Start with what an MCP server is.