Claude.ai, Claude Desktop, and Cowork
Connect Pushary to claude.ai, the Claude Desktop app, or Claude Cowork by pasting one link, so Claude can notify you and ask you questions on your phone
You can connect Pushary to claude.ai (web), the Claude Desktop app, Cowork, and the Claude mobile apps by pasting one link. No terminal, no install, no config files.
Once connected, Claude can send you notifications and ask you questions on your phone while it works. This is the cooperative path: Claude chooses when to call the tools. It does not stop Claude mid task. To approve risky commands before they run, use an agent with hooks like Claude Code (see Supported agents).
There is no shell to gate on these surfaces, so there is nothing to enforce. What you get is the part that fits them: Claude pings you and asks you on your phone during long tasks.
Get your connector link
The connector link is a dedicated, revocable key. It is not your full API key, and it can only send notifications and ask questions. Generate it from the dashboard:
- Open Settings, Connections in your dashboard
- Find the Claude (claude.ai, Desktop, and Cowork) section
- Click Get connector link
- Copy the link. It looks like
https://pushary.com/api/mcp/mcp?api_key=pk_xxx.secret_xxx
Treat this link like a password. Anyone who has it can send notifications to your devices until you revoke it. You can revoke or regenerate it any time from the same Connections section. The link also expires on its own after 90 days; the Connections section shows a countdown when it gets close, and after rotating you re-paste the new link in Claude.
Add it in Claude
- In Claude, open Settings
- Go to Connectors (on claude.ai this lives under Customize, then Connectors)
- Click Add custom connector
- Leave the OAuth fields empty. Paste your connector link into the Remote MCP server URL field
- Give it a name like
Pusharyand click Add
That is it. The dashboard flips the Claude section to Connected once Claude completes the handshake.
Use it in Cowork
Connectors are configured at the account level and brokered through your Claude account, so the connector you just added works inside Cowork sessions too, on desktop, web, and mobile.
- Open a Cowork session
- Open Customize (or the + icon in the chat bar), then Connectors
- Turn on Pushary for the session
Cowork runs long tasks, often while you are away, which makes the connector most useful when Claude reaches for it on its own. Cowork does not read a repo memory file, so give it standing instructions once: in the Claude app, open Settings, then Cowork, and paste this into your standing instructions.
Pushary is connected as a custom connector. Use it proactively to reach me on my phone. Do not wait for me to ask.
- When you need a decision or a clarifying answer, call ask_user instead of guessing or stalling. Use type "confirm" for yes or no, "select" for a fixed set of options, and "input" for free text.
- Before any risky or irreversible step (deleting or overwriting files, spending money, sending anything external, bulk changes), call ask_user with type "confirm" and wait for my approval.
- When a task finishes, or when you are blocked or hit an error you cannot resolve, call send_notification with a short summary so I know.
- On long tasks where I might be away, prefer send_notification with context.askQuestion over a blocking ask_user, so I can answer from the notification page when I pick up my phone.
- A question stays open for 10 minutes. If wait_for_answer returns without an answer, call wait_for_answer again with the same question id before giving up.
- Pass agentName as "Claude Cowork - <task name>" on every call so I know which session is asking.
- Use cancel_question to retract a question that is no longer needed.The same block is available with a copy button in Settings, Connections. With the agentName convention in place, Cowork sessions show up in your Activity feed and Fleet view as Claude Cowork, grouped by task.
Cowork may ask you to approve connector tool calls inside the session, and depending on your version the "Allow always" option may not be offered for custom connectors. If you see repeated approval prompts for Pushary calls, keep the standing instructions focused on the moments that matter (risky steps and completion) rather than frequent check-ins.
Long, unattended sessions
A blocking question waits about 55 seconds per wait_for_answer call, and a question stays answerable for 10 minutes. Cowork sessions can run much longer than that while you are away. Two patterns cover it:
- For decisions Claude needs soon,
ask_userthen repeatedwait_for_answercalls with the same question id. - For everything else,
send_notificationwithcontext.askQuestion. You get a normal push, and the answer form sits on the notification page whenever you pick up your phone. Missed questions also appear in the pending inbox on your subscribe page.
What Claude can do
The connector exposes four tools: send_notification, ask_user, wait_for_answer, and cancel_question. See the tools reference. It cannot read your subscribers or send campaigns, even though it rides on the same link.
A blocking question waits for your answer for up to about 55 seconds. If you need longer, Claude can check again with wait_for_answer using the same question id (questions stay open for 10 minutes).
Prompts to try
Get pinged when a long task finishes:
When you finish this task, use Pushary to send me a notification with a short
summary of what changed.Ask before something irreversible:
Before you do anything destructive or irreversible, use Pushary to ask me to
confirm, and wait for my answer before continuing.Revoke or rotate
Open the same Settings, Connections section and use Revoke link to kill the connection, or Generate new link to rotate it. The old link stops working immediately. After rotating, update the URL in Claude under Settings, Connectors.