Your agent has a question.
Answer it in one tap.
Nudgio lets any AI agent ask you for a decision and get your answer back. One MCP tool call for the agent, one tap for you. No Slack workspace, no callback server, no waiting at your desk.
Hi Nick, thanks for the updated drawing. We can meet the 14th if the connectors arrive by Friday…
How it works
Three steps, and the middle one is you.
The agent asks
It calls ask with a question, up to four buttons and an optional text reply.
You answer
Tap a button or type a short reply. Read the full draft first if you want to.
The agent carries on
Your answer comes back as the tool result, or by signed webhook. If nobody answers, the agent is told that too.
Connect in one line
Works with any MCP client. Claude and ChatGPT connect with a sign-in; Claude Code, scripts and n8n use a key.
claude mcp add --transport http nudgio https://nudgio.co.uk/mcp \
--header "Authorization: Bearer ndg_your_agent_key"
ask({
title: "Send reply to Nick at Astute?",
body: draft,
options: [{ id: "send", label: "Send" }, { id: "hold", label: "Hold" }],
allow_text: true,
wait: 55
})
→ { status: "answered", answer: { option_id: "send", text: "change the second line" } }
Built around the question, not the message
Notification services tell your phone something. Nudgio asks, and tells your agent what you said.
The answer comes back
No endpoint for you to host. ask and wait_for return the answer; webhooks are there for agents that cannot block.
A definite outcome
Every request ends as answered, expired or cancelled, so an agent can reason about silence.
Typed replies
“Yes, but change the greeting” is a normal answer, not an edge case.
One identity per agent
Each agent has its own name, key, mute switch and revoke. One phone, many agents, no crossed wires.
An audit trail
Who approved what, when and from which device, with the context the agent attached.
Safe to retry
Idempotency keys mean a retrying agent cannot ask you the same thing twice.
Where you answer
Today you answer in the web inbox, on any device. Native iOS, Android and macOS apps with lock-screen buttons are in development and will use the same account.
