
Let your coding agent ask you first, on your phone, before it does something you can't undo.
Let your coding agent ask you first, on your phone, before it does something you can't undo.
·
Let your coding agent ask you first, on your phone, before it does something you can't undo.
Agent: About to drop and recreate `users` on staging. Approving?
Phone: [ Approve ] [ Deny ] ← optionally behind your fingerprint
Agent: APPROVED after 34s. Confirmed by biometric.Works with Claude Code, Cursor, Windsurf, or anything else that speaks MCP.
Get a token in the Lauther app: Apps → + → New token. Then add the server to your MCP config:
{
"mcpServers": {
"lauther": {
"command": "npx",
"args": ["-y", "lauther-mcp"],
"env": { "LAUTHER_TOKEN": "lpt_your_token" }
}
}
}Nothing to install — npx fetches it. Node 18+.
ask_approvalBlocks until you answer, then tells the agent one of three things:
| Result | What the agent is told |
|---|---|
APPROVED | proceed with exactly what was asked, and nothing further |
DENIED | stop; do not retry, do not find another way |
NO ANSWER | stop — silence is not consent |
That last row is the one that matters. A timeout is not a yes, and the tool says so in words the model has to read.
Options: details for context, require_biometric to demand a fingerprint,
timeout_seconds for how long you're willing to wait (default 120).
On waiting. Lauther's API long-polls for at most 25 seconds. Past that this server keeps asking about the same notification rather than sending another, so a ten-minute wait still puts one question on your phone — not one every half minute.
send_notificationOne-way: "the migration finished", "the build broke". Takes title,
message, priority and url. Only urgent crosses your quiet hours.
It reports what actually happened, including the case worth knowing about: if no device is registered on your account, you're told that rather than given a cheerful success for a notification nobody received.
get_locationAsks you to share where you are, once. You get a prompt on your phone with Share location and Decline; the agent receives one position, as it was when you tapped.
| Result | What the agent is told |
|---|---|
SHARED | latitude, longitude, accuracy in metres, and when it was read |
DECLINED | do not retry and do not find the location another way |
NO ANSWER | silence is not consent; nothing was shared |
EXPIRED | the request lapsed on your phone; nothing was shared |
Options: question (what you see on the prompt), details,
require_biometric, timeout_seconds (default 120).
request_photoAsks you for one picture, taken on the spot or picked from your library. The agent gets the link and the image itself, so it can look at it. The link works for 7 days, after which the photo is deleted. If the image cannot be fetched the agent still gets the text and the link.
Same options and the same four outcomes as get_location.
ask_textAsks you a short question and waits for you to type the answer on your phone: a verification code, a choice, a name, a fact only you know. The prompt shows the question and a field, with Reply and Decline. Answers run to 500 characters, so it is for short things.
| Result | What the agent is told |
|---|---|
ANSWERED | exactly what you typed, in quotes |
DECLINED | do not retry and do not get the answer another way |
NO ANSWER | silence is not consent; nothing was sent |
EXPIRED | the request lapsed on your phone; nothing was sent |
Options: question (default "Answer a question?"), details,
placeholder (a hint in the field, such as "6-digit code"),
require_biometric, timeout_seconds (default 120).
Most models won't reach for an approval tool unless asked. Something like this in your project rules works well:
Before anything irreversible — deploying, deleting data, spending money,
force-pushing, emailing real people, touching production — call
ask_approval and wait. Proceed only on APPROVED.The approval is signed and, when you ask for it, biometric — the answer records that a person confirmed it, not merely that something clicked. That is the difference between an audit trail and a log line.
lauther-client — the plain Node client,
if you want push and approvals in your own code rather than in an agent.MIT
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add lauther -- npx -y lauther-mcp{
"mcpServers": {
"lauther": {
"env": {
"LAUTHER_TOKEN": ""
},
"args": [
"-y",
"lauther-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"lauther","env":{"LAUTHER_TOKEN":""},"args":["-y","lauther-mcp"],"command":"npx"}'[mcp_servers.lauther]
command = "npx"
args = ["-y", "lauther-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/lauther-mcp to learn what the "Lauther Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/lauther-mcp)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "lauther-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.