Connect any agent

Pushary works with any agent that can call an MCP server or send an HTTP request: an ops bot, a research agent, an n8n or Zapier workflow, a LangGraph graph, or a Python script. The agent sends you a question, your phone shows it, and the agent continues with your answer. You need an API key and nothing else.

Set PUSHARY_API_KEY to your key, then ask your first question:

curl -X POST https://pushary.com/api/v1/server/ask \
  -H "Authorization: Bearer $PUSHARY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Deploy the new build to production?"}'

Your phone shows a yes or no question. Answer it and the call returns "answered": true with "value": "yes" or "value": "no".

Get your API key

export PUSHARY_API_KEY="pk_xxx.xxx"

No question on your phone? Install the Pushary app from the App Store or Google Play, sign in with the same account, and try again.

Ask a question and wait for the answer

POST https://pushary.com/api/v1/server/ask sends the question to your phone app. It can also reach your browser and Slack, if you connected them. By default the call blocks until you answer, for up to 30 seconds.

curl -X POST https://pushary.com/api/v1/server/ask \
  -H "Authorization: Bearer $PUSHARY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "Send the campaign to all 4,000 contacts?",
    "type": "confirm",
    "agentName": "Marketing agent",
    "timeoutSeconds": 50
  }'

An answered question returns:

{
  "correlationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "question": "Send the campaign to all 4,000 contacts?",
  "type": "confirm",
  "status": "answered",
  "answered": true,
  "value": "yes"
}

The response also carries liveUrl (a page where you can answer), pollUrl, expiresInSeconds (600) and mode (your approval mode).

Proceed only when answered is true and value is "yes". Anything else is not a yes.

Request fields

Ask without blocking, then poll

Set "wait": false and the call returns at once with "status": "pending" and a pollUrl:

{ "correlationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "status": "pending", "answered": false, "pollUrl": "https://pushary.com/api/v1/server/ask/a1b2c3d4-e5f6-7890-abcd-ef1234567890" }

Poll it with GET. Add ?wait=30 to hold the request open for up to 30 seconds (maximum 55):

curl "https://pushary.com/api/v1/server/ask/a1b2c3d4-e5f6-7890-abcd-ef1234567890?wait=30" \
  -H "Authorization: Bearer $PUSHARY_API_KEY"

status is pending, answered, expired or cancelled. An unknown ID returns 404.

Cancel a question you no longer need:

curl -X DELETE "https://pushary.com/api/v1/server/ask/a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  -H "Authorization: Bearer $PUSHARY_API_KEY"

The response says "cancelled": true when a pending question was removed. false means it was already answered, expired or cancelled.

Get the answer on a webhook

Use a webhook when your process cannot wait, for example an n8n or Make workflow. In n8n or Make, pass the URL of a node that waits for a webhook as callbackUrl. The workflow resumes when the answer arrives.

curl https://pushary.com/api/v1/server/webhook-secret \
  -H "Authorization: Bearer $PUSHARY_API_KEY"

curl -X POST https://pushary.com/api/v1/server/ask \
  -H "Authorization: Bearer $PUSHARY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "Email the refund confirmation to the customer?",
    "wait": false,
    "callbackUrl": "https://your-app.com/webhooks/pushary"
  }'

{
  "correlationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "answer": "yes",
  "value": "yes",
  "answeredAt": "2026-10-04T12:00:00.000Z",
  "context": "Only present when you passed context"
}

import crypto from 'node:crypto'

const isFromPushary = (rawBody: string, signature: string, secret: string): boolean => {
  const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex')
  return expected.length === signature.length
    && crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature))
}

The callback fires only when someone answers, never on a timeout or a cancel. Return a 2xx status within 10 seconds. Pushary does not follow redirects, and it retries a failed delivery up to 12 attempts in total, so handle the same correlationId twice safely.

Send a one-way notification

The MCP send_notification tool reaches your phone app and your browser. You can call it over plain HTTP, with no MCP library:

curl -X POST https://pushary.com/api/mcp/mcp \
  -H "Authorization: Bearer $PUSHARY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"send_notification","arguments":{"title":"Backfill finished","body":"Processed 12,400 rows with 0 errors."}}}'

title takes up to 100 characters and body up to 500. The limit is 10 notifications per 5 minutes per site.

POST /api/v1/server/send reaches browser push subscribers only. It does not reach the Pushary phone app. If nobody has subscribed in a browser, it returns 400 No subscribers found matching criteria.

Connect an MCP client

Point any MCP client at the Pushary endpoint. The agent then has ask_user, wait_for_answer, cancel_question, send_notification and propose_scope as tools.

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

The official MCP SDKs for TypeScript and Python connect with only the URL and the Authorization header. A custom agent, or a LangChain or LangGraph tool, can use the same settings. For the approval patterns, see Human in the loop.

Cline

Run npx pushary@latest setup --agents cline. It adds Pushary to Cline's MCP settings with your key, and a global rule that tells Cline to ask and notify through Pushary.

To add it by hand, edit ~/.cline/data/settings/cline_mcp_settings.json, the file Cline 4 reads for both the VS Code extension and the Cline CLI. Cline does not fill in ${PUSHARY_API_KEY}, so paste the key itself. Keep "type": "streamableHttp": without it Cline falls back to the older SSE transport and cannot connect to this URL.

{
  "mcpServers": {
    "pushary": {
      "type": "streamableHttp",
      "url": "https://pushary.com/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer pk_your_key"
      },
      "timeout": 90
    }
  }
}

Then reload VS Code (Developer: Reload Window). Cline asks before each MCP tool call unless Use MCP servers is ticked in its Auto-approve menu. That setting covers every MCP server in Cline, not only Pushary, so tick it only if you are happy for all of them to run without a click.

Name your agent

Pass agentName (and sessionId if you have one) on every call. The dashboard and the Fleet Board then label the work with your agent's name instead of a generic session. Several agents running at once each show up on their own.

Errors and limits

If your approval mode is In agent, /ask sends no push and the response says "mode": "terminal_only". To get every question on your phone, open the Pushary app, tap Questions & approvals at the top of your inbox, and pick Always. See Permission policies for all four modes.

Next steps