Grok Bot
Connect Pushary to Grok Bot so your Bots send you a push when work finishes or fails, and ask you questions you answer from your phone.
Grok Bot runs your Bots on a cloud computer that keeps working after you close the laptop. Pushary tells you how that went. A Bot sends you a push when a routine run or a long task finishes or fails, and asks you a question when it needs a decision only you can make. You answer from the Pushary phone or Mac app, in the same inbox as your other AI agents.
You need a paid Pushary plan for your own agents, such as Agent, Agent Pro or Team, and the Pushary app on your phone, or the Mac app, signed in to the same account. Partner plans embed approvals in your own product and do not include this. Nothing is installed on your computer.
This guide is for the Grok Bot app. For Grok Build, xAI's terminal coding agent, run npx pushary@latest setup and pick Grok Build; see Supported agents.
Grok Bot chooses when to call Pushary. Pushary cannot stop a Bot in the middle of a task, and Grok Bot keeps its own approval cards for the actions it gates. To approve risky commands before they run on your own machine, use an agent with hooks, such as Claude Code or Codex. Supported agents shows which agents Pushary can enforce.
Add Pushary to Grok Bot
Pushary's listing in Grok Bot's Connect apps is waiting for review by Cursor, which runs the catalog. Until it is approved, searching Connect apps for Pushary finds nothing. Add Pushary as a custom MCP server instead. It is the same connection, and it works today.
Ask a Bot to add the server
In any Bot's chat, send:
Add a custom MCP server called pushary at https://pushary.com/api/mcp/mcpSay "custom MCP server" so the Bot adds this server and does not look for a catalog plugin.
Confirm it
The Bot shows the name and URL and asks you to confirm. Check that the URL is exactly https://pushary.com/api/mcp/mcp, then choose Add it (or Save). If the card offers an OAuth Client ID and Client Secret, leave both empty: Grok Bot registers itself with Pushary when you sign in. Add no header and no API key.
Sign in
The Bot posts a connect card. Choose Authorize, sign in with the same Pushary account your phone uses, and choose Allow access. Grok Bot's documentation says the sign-in stays on its connector service and your Bots use the tools without receiving it.
Send a test question
Attach Pushary to the chat by typing @ and picking pushary, then send:
Use Pushary to ask me "Did this reach you?" as a yes or no question, with
agentName "Grok Bot - Setup check". Wait for my answer and tell me what I chose.Answer it on your phone. The Bot telling you your answer confirms the connection.
The server is added for your whole account, so every Bot can use it. It is listed under Settings > Plugins > Yours.
Tell your Bots when to use it
A custom server brings the tools but not the rule that comes with the listing. Add these instructions to a Bot's skill, or paste them into a chat, so the Bot reaches you on its own:
Pushary is connected. When a routine run or long task finishes with a result worth
seeing, call send_notification with context.type "task_complete" and a short
summary. When work fails and you cannot fix it, use context.type "error". When you
need a decision only I can make and no approval card is already asking, call
ask_user. Send at most one notification per routine run and three per task. On
every response, follow handoffAction first when present, otherwise
nextAction: on "stop", stop; on "cancel_then_ask_in_current_client", cancel the
question; if the cancel returns cancelled false, call wait_for_answer once with
timeoutMs 1000 and honor any answer that won; if it returns cancelled true, ask in
this chat; while it says wait_for_answer, keep waiting with the same correlationId.
Only a pending question is live, and silence is never consent. Pass agentName as
"Grok Bot - <task>" on every call. Never send passwords, keys, codes or payment
details through Pushary.Add Pushary from Connect apps, once it is listed
When searching Connect apps for Pushary finds it, choose Add and sign in the same way. The listing brings an always-on rule that tells each Bot when to reach you: one push per routine run at most, a question only for a decision you have to make, and no question that a Grok Bot approval card is already asking. After adding it, remove the custom pushary server under Settings > Plugins > Yours, so your Bots do not see the same tools twice.
What a Bot can do with Pushary
A Bot gets six tools: send_notification, ask_user, wait_for_answer, cancel_question, schedule_reminder and propose_scope. See the tools reference. It cannot read or change your policies, subscribers, campaigns or API keys.
ask_user waits up to about 55 seconds per call. A Bot keeps checking with wait_for_answer and the same question id. A question nobody answers expires after about ten minutes, and an expired question is never treated as a yes.
Everything you connect by signing in to Pushary, such as Claude and every Bot, shares one limit: 10 notifications or reminders per 5 minutes and 25 open questions. The listing's rule and the instructions above keep a Bot to one notification per routine run, so several Bots on schedules stay well under it.
With agentName set, your Bots show up in your Activity feed as Grok Bot.
Disconnect
Remove the custom pushary server where Grok Bot lists it under Settings > Plugins > Yours, or ask a Bot to remove the custom pushary MCP server. If you added the listing, remove Pushary from Connect apps. Your Bots stop using the sign-in connection. Your Pushary account and its history stay as they are.
Troubleshooting
Searching Connect apps for Pushary finds nothing
The listing is still in review. Add Pushary as a custom MCP server with the steps above.
The Bot added something else
Ask again with the words "custom MCP server" and the full URL https://pushary.com/api/mcp/mcp.
The Bot says Pushary is not connected
Check Settings > Plugins > Yours for the pushary server, sign in again if it asks you to, and attach it to the chat with @. If a team admin manages your Grok Bot plugins, Pushary may show Disabled by team admin. Ask them to enable it on the team's plugins page and, on Enterprise, add https://pushary.com/api/mcp/mcp to the MCP allowlist, then restart Grok Bot.
The notification reached 0 devices
The send_notification result warns "Notification reached 0 devices" when no phone or browser is connected to your workspace. Install the Pushary app and sign in with the same account. See Receiving notifications.
Bots never reach out on their own
A custom server does not bring the rule. Add the instructions above to the Bot's skill. Once the listing is approved, adding Pushary from Connect apps brings the rule with it.