lauther-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAUTHER_TOKEN | Yes | Your Lauther API token, used to authenticate pushes and approval questions sent to your phone. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_approvalA | Ask the human who owns this machine to approve or deny something, on their phone, and wait for the answer. Use this BEFORE anything irreversible or expensive: deploying, deleting data, spending money, sending mail to real people, force-pushing, touching production. Returns APPROVED, DENIED, or NO ANSWER. Proceed only on APPROVED — a denial and a timeout both mean stop. |
| send_notificationA | Tell the human something, on their phone. Use for finishing a long job, a build breaking, or anything worth interrupting them for. This does NOT wait for a reply — use ask_approval when you need permission. |
| get_locationA | Ask the human who owns this phone to share where they are right now. They get a prompt and choose Share or Decline; if they share, one position is sent, once, as it was at that moment. Use it when you need their location to do the task (find the nearest branch, set a timezone, log a site visit), not to track them. Returns SHARED with latitude, longitude and accuracy, or DECLINED, NO ANSWER or EXPIRED. On anything but SHARED you have no location: do not guess one. |
| request_photoA | Ask the human who owns this phone for one picture. They get a prompt and choose to take a photo (or pick one) or Decline. Use it when you need to see something only they can show you: a label, a screen, a whiteboard, a damaged part. Returns SHARED with a link plus the image itself so you can look at it directly, or DECLINED, NO ANSWER or EXPIRED. The link works for 7 days and the photo is then deleted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: ask_approval blocks for a yes/no decision, send_notification is fire-and-forget, get_location requests a one-shot position, and request_photo requests a one-shot image. The descriptions explicitly draw the approval-vs-notification boundary, so an agent cannot easily confuse them.
All four names follow a consistent verb_noun snake_case pattern (ask_approval, send_notification, get_location, request_photo). The verb variety is semantically motivated rather than arbitrary, and the pattern is perfectly predictable.
Four tools is a tight, well-scoped surface for a phone-based human-in-the-loop bridge. Every tool covers a genuinely distinct interaction type and none feels redundant or filler.
The surface covers the main human-interaction needs: permission, notification, location, and visual input. A minor gap is the absence of a way to ask a free-form question and get a text answer back, since ask_approval only returns APPROVED/DENIED/NO ANSWER.