Pushary for Cursor

A control panel for your AI coding agent. Get a push when work finishes, answer the agent from your phone, and approve risky commands before they run.

---

What it is

Pushary connects Cursor to your phone. When the agent finishes a task, needs a decision, or is about to run something risky, it reaches you with a push notification. You answer from the lock screen and the agent keeps going. It works even when you have stepped away from your computer.

What it does

There are three things.

1. Notify. The agent sends a push when a long task finishes, or when a build, test, or deploy fails. The push can include what changed, the error, and suggested next steps.

2. Ask. The agent asks you questions through push: yes or no, multiple choice, or free text. It waits for your answer. The bundled instructions guide the agent to use Pushary for questions. Native editor question dialogs are not automatically intercepted.

3. Gate. Shell commands, file writes/edits/deletes, and third-party MCP calls reach your Pushary policy before execution. The policy can approve, deny, or wait for your answer. Cancelled or unverifiable decisions stop the action. Cursor’s generic file-tool hook does not enforce ask, so an unresolved file action is denied. File actions explicitly marked not_gated by the server proceed; shell/MCP hooks can hand off to Cursor’s prompt.

Install

You need two things: the plugin, and an API key.

Option 1: Cursor Marketplace (recommended)

Open the Marketplace panel in Cursor, search for Pushary, and click install. Then set your API key (see below).

Option 2: CLI

This also sets up Claude Code, Codex, and Hermes if you use them.

npx @pushary/agent-hooks@latest setup

Option 3: Manual MCP

Add this to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "pushary": {
      "type": "http",
      "url": "https://pushary.com/api/mcp/mcp",
      "headers": { "Authorization": "Bearer ${env:PUSHARY_API_KEY}" }
    }
  }
}

The plugin and CLI installer use the same decision service. Manual MCP-only configuration provides questions and notifications, but does not install approval or activity hooks.

Set your API key

The plugin reads your key from the PUSHARY_API_KEY environment variable. Get a key at https://pushary.com, then add it to your shell profile:

echo 'export PUSHARY_API_KEY="pk_xxx.sk_xxx"' >> ~/.zshrc
source ~/.zshrc

Install the Pushary app on your phone (or turn on web push) so the agent can reach you.

Troubleshooting

macOS GUI apps do not read .zshrc. If Settings > MCP shows pushary in red after you set the env var, launch Cursor from a terminal where PUSHARY_API_KEY is exported, or set the variable system-wide so GUI apps see it.

What is in the plugin

Part	File	What it does
MCP server	mcp.json	Connects Cursor to the Pushary tools: send_notification, ask_user, wait_for_answer, cancel_question, list_sessions
Rule	rules/pushary.mdc	Always on guidance so the agent uses Pushary on its own
Skill	skills/pushary/SKILL.md	Full tool reference: parameters, examples, return values
Hook	hooks/hooks.json and scripts/pushary-gate.mjs	Evaluates tool approvals and reports session/tool activity
Commands	commands/	/pushary-test and /notify-when-done

How the gate decides

The hooks register the supported execution boundaries; your dashboard policy decides which actions need approval. No shell-command regex hides a tool from policy evaluation. Lifecycle hooks report session starts, turn completion, tool results, compaction, and subagent activity.

Timeout approvals apply only after the configured wait actually elapsed. Short editor hook budgets can end a wait earlier; cancellation is attempted before handoff. An uncertain cancellation denies the action. Local plugin installation does not install hooks into remote or cloud agent environments.

Commands

• /pushary-test sends a test push so you can confirm delivery.
• /notify-when-done tells the agent to push a summary when the current task finishes.

Development

skills/pushary/SKILL.md mirrors the Pushary skill that ships with @pushary/agent-hooks. Keep the two the same.

Test the plugin locally before publishing:

ln -s "$(pwd)" ~/.cursor/plugins/local/pushary

Then reload Cursor with Developer: Reload Window.

Security

This repository has no secrets. Your key is read at runtime from PUSHARY_API_KEY. The gate script has no dependencies and only talks to pushary.com. Read scripts/pushary-gate.mjs to see exactly what it sends. See SECURITY.md for details.

License

MIT. See LICENSE.