Not on 0.6.31 or later. mcpo is for MCP servers that only run locally over stdio; LFG Alarm is a remote Streamable HTTP server.

A time alarm is a real alarm on iPhone and Android and rings through silent mode. An anything alarm rings full screen on Android; on iPhone it arrives as a time-sensitive alert with the alarm's sound, so keep the ringer on.

Does LFG Alarm see our chats?

No. LFG Alarm only receives what Open WebUI sends when it uses LFG Alarm's tools.

Connect LFG Alarm to Open WebUI

Before you start

Get the LFG Alarm app on your phone from Google Play or the App Store, and sign in. Open WebUI makes the alarms; the app is what rings them.
Open WebUI 0.6.31 or later. That version added native MCP over Streamable HTTP, which is what LFG Alarm speaks, so no bridge such as mcpo is needed.
Admin access. Only admins can add MCP servers in Open WebUI.
A steady WEBUI_SECRET_KEY. Open WebUI's docs say to set it, or OAuth connections break each time the container restarts.

Connect it

Open Settings > Admin > Integrations, in the External Tool Servers section.
Click + Add Connection.
Type: MCP (Streamable HTTP). Picking the OpenAPI type by mistake can leave the page loading forever.
Server URL: https://mcp.lfg.gm.
Auth: OAuth 2.1. LFG Alarm registers Open WebUI on its own, so there is no client ID to create.
Click Save, and restart Open WebUI if it asks.
In a chat, turn on LFG Alarm in the tools. The first time, a window opens on lfg.gm: sign in with your LFG Alarm account and tap Allow.

The server must be reachable from the Open WebUI backend, not only from your browser; https://mcp.lfg.gm is a public address, so a normal internet connection is enough. These steps follow Open WebUI's own docs; menus have moved between versions, so if a label differs, look for External Tools or Integrations in the admin settings.

Why OAuth 2.1 and not Bearer

With OAuth 2.1, each person on your Open WebUI signs in to their own LFG Alarm account, so their alarms ring on their phone. Bearer sends one key for everyone. An LFG Alarm personal key acts as its owner, so with Bearer every user would be setting alarms on one person's phone. Use Bearer only on an Open WebUI that is yours alone.

Use it in a chat

Open WebUI is often a household or small-team setup on a home server. Lena runs one for her flat: each flatmate signs in once, and "wake me at 6:45 on weekdays" sets an alarm on whoever asked. Sam uses a local model through Open WebUI and asks it for an anything alarm, then pastes the private link into his backup script so a failed backup rings him. See How to make any app, script or feed ring your phone.

Smaller local models can struggle to pick the right tool. If yours does, name it: "Use LFG Alarm to...".

Try it

try this

Have your AI agent make it.

Paste this into ChatGPT, Claude, Grok or any AI agent that can add a connector, not into the LFG Alarm app. The setup steps come with it: get the LFG Alarm app, connect it to your agent once, and your agent makes the alarm in your account.

Use LFG Alarm to set a one-off time alarm for 6:45 tomorrow called "Run". Then tell me the date and time it will ring.

Already have the LFG Alarm app and connected it to your AI agent?

Why it works. A one-off time alarm and the time read back, which proves the connection, the sign-in and the model's tool use all work.

More ideas: "Wake me at 7:00 every weekday and call it Get up", or "List my alarms". See Using LFG Alarm from your AI agent.

If it does not work

The tool asks to sign in on every restart. Set WEBUI_SECRET_KEY to a fixed value.
The page hangs after saving. The connection type is OpenAPI; change it to MCP (Streamable HTTP).
The model never calls LFG Alarm. Check LFG Alarm is on for this chat, and try a model with stronger tool use.
Still stuck? Write to us from the support page.

Learn more

Sources and further reading

LFG Alarm is not affiliated with Open WebUI.