Let your AI assistant ask you — on your phone
Agent work got long, and it got interactive. A migration, a refactor across a directory, a deploy. You start it and walk away, because watching a terminal for ten minutes is not a use of a human.
The obvious failure is that it finishes and you do not know. The one that actually costs you is quieter: it stops a minute in, waiting for a decision you would have made instantly, and then sits there until you come back.
Reflecto is a bridge between your Android phone and your computer — it mirrors your notifications, syncs your clipboard, moves files. It also runs a hosted MCP server, which is what this post is about: once your assistant is connected, it can reach that same phone.
The interesting part is that it can ask, not just tell
Sending a notification when a job finishes is the ordinary case, and useful enough.
The part worth the setup is that your assistant can ask you something and wait.
It creates a question with two to four choices. Your phone gets a high-priority notification with those choices on it. You tap one. The assistant is still sitting there, polling, and it picks up your answer and carries on.
You do not have to prompt for this every time. The MCP server ships instructions telling the model to use it when it needs a decision before a consequential action and you might be away — so a well-behaved assistant reaches for it on its own.
Some numbers, because they change how you use it. A question stays open for ten minutes by default, and the assistant can ask for up to a day. Each poll waits up to 45 seconds — assistant clients tend to hang up around a minute — and then it polls again. What comes back is the index of the choice you tapped, an integer; the server never stores the labels, so the answer record holds no text at all.
Connecting it
You need the Reflecto app on an Android phone — it is on Google Play, free, no account, no email. You do not need to pair a computer: the phone alone can receive, and the app has a path for setting up an assistant without linking one.
In Claude Code, one command:
claude mcp add --transport http reflecto https://api.reflecto.dev/mcpIn the Claude app, go to Customize → Connectors, click +, then Add custom connector, and enter:
https://api.reflecto.dev/mcpAnthropic documents custom connectors on Free, Pro and Max as well as Team and Enterprise, so this does not need a paid tier. On Team and Enterprise the path is different — Organization settings → Connectors — and only an Owner can add one, which is worth knowing before you try it on a work account.
Either way you will not be asked for an API key, because the connector does not use one. You get a six-digit code instead. Open Reflecto on your phone and approve the connection with that code.
That is deliberate, and it is the part we would defend hardest. Pasting a long-lived secret into a third-party service is the normal way to do this. Here there is no secret to paste, nothing to rotate, and nothing to leak — the connector holds a grant your phone issued, and your phone can revoke it from Settings → Connected services.
Ask your assistant to send you a test notification. If it arrives, you are done.
What your assistant can do
send_notification— a message to your devices, with an optional title, priority, link and up to three buttons.request_approval— ask a question with two to four choices.check_reply— wait for the answer.list_devices— names, types and whether they are online, so it can target one. Metadata only, never notification content and never your keys.find_my_phone— rings it. Stops itself after a minute.
What is not encrypted, and why
Reflecto is end-to-end encrypted. Notifications mirrored from your phone are encrypted on the phone and decrypted on your computer, and the server routes sealed envelopes it cannot open.
Messages from your assistant do not work that way, and it would be dishonest to imply they do.
The reason is structural rather than an oversight. End-to-end encryption needs the sender to hold a key. Your assistant is not one of your paired devices and holds no keys, so there is nothing on the sending side to encrypt with. The server composes the message: your text arrives, is held in memory only long enough to encrypt it separately to each of your devices, and is never written to disk.
To be exact about the question-and-answer flow too, since it is easy to over-claim here: the answer record really is just an integer, but the question travels the same server-composed path as any assistant message. The server sees the text, briefly, in order to encrypt it to your phone.
That is a real difference in what the server can see, and it is the same trust model as our public send API. We document it rather than round it off, because a product claiming encryption everywhere while quietly holding an exception is worse than one that tells you where the exception is.
Practically: this is fine for “deploy finished, 3 tests failed” and for “shall I force-push?”. Do not have your assistant send secrets through it.
What it does not do
It does not read your notifications, your messages or your screen. Nothing here
gives an assistant a way to look at your phone — list_devices returns names and
online status and stops there.
You need an Android phone. Reflecto’s mirroring cannot work on iOS, because no third-party app there can read another app’s notifications. Assistant messages are a different matter — iOS would permit those; we simply have not built it.
Why not just use a webhook?
You can, and it will reach your lock screen. Several people have built notification MCP servers already, some specifically for Claude Code, and most route through a chat account you already have or a push service you sign up for separately.
What is different here is that the message arrives on the phone you already set up, with no new account anywhere — and if you also use Reflecto to mirror your notifications, it lands in the same place as those. The assistant can also ask rather than only tell, which is what turns a notification channel into something that keeps work moving while you are away from the desk.
It is free, there is no message quota, and setup is a single command and a six-digit code. Get the app, or read the API docs first.
If you try it and it does not work, there is a feedback option in the app and it reaches a human.