> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Uptime Kuma

> Connect an existing instance and manage its monitors through the agent.

Open **Connectors → Connect → Uptime Kuma** as an Administrator. Supply a label,
the instance base URL and either its supported auth token or username/password.
Enter secrets in the secure form, not the conversation. The instance must be
reachable by the Nuphos backend under its URL restrictions.

## Verify

After connecting, select the binding and ask for a list of existing monitors.
Check their target and status rather than creating a new monitor as an auth test.
Credentials are held server-side; the agent uses Nuphos monitor endpoints.

## Monitor changes

The agent can create, update, pause, resume or delete monitors where supported.
Specify the exact URL, monitor type, interval and intended notifications. A
monitor existing is not proof that a notification reaches the intended person;
verify notification wiring separately. Uptime Kuma's dedicated pages are
separate from the [unified Monitoring overview](https://docs.nuphos.ai/observability/monitoring.md).

## Troubleshoot and disconnect

Check URL, instance health and credentials if reads fail. Do not expose a
private monitoring instance broadly to make it reachable. Remove the binding
and revoke the instance credential when retiring access. Disconnecting does not
stop its monitors; explicitly pause or remove those you intend to stop.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.