OneUptime

What OneUptime does

OneUptime provides MCP access to selected OneUptime project records. The available resource groups are Teams, Labels, Security Cases, Security Case Notes, and Security Detections. For each group, the server exposes operations for creating records, retrieving an individual record by ID, searching collections, modifying existing records, deleting records, and counting matching records.

The server is suited to agent workflows that need to maintain operational ownership data, classification labels, or security-related records in OneUptime. It can also support reporting or existence checks by returning counts without requiring a full collection listing.

How it works

Tool calls operate against OneUptime and return either an individual resource, a collection response, a count, or a deletion confirmation. Collection queries can include filtering, pagination, and sorting, allowing an agent to narrow results or process records in pages. The list tools also return the total number of matching records alongside the returned objects.

Project identification is handled through the API key. Calls that create resources do not require a separate project ID, because the project is inferred from that credential. To work with a particular record, an agent can first use the relevant list tool to find its ID, then call the corresponding get, update, or delete tool.

Updates are partial: only supplied fields are changed, so omitted fields retain their existing values. After an update, the matching get operation can be used to inspect the resulting record.

Tools and capabilities

• Manage Teams with create_team, get_team, list_teams, update_team, delete_team, and count_teams.
• Manage Labels with the corresponding create, get, list, update, delete, and count operations.
• Manage Security Cases, including filtered searches and record counts.
• Add and maintain Security Case Notes with full CRUD and count operations.
• Create, inspect, search, modify, remove, and count Security Detections.
• Use collection filters, pagination, sorting, and total-match counts on list operations.

The delete tools permanently remove their target records and return a confirmation after a successful deletion. The delete operation is available for every resource group exposed by the server.

Limitations and notes

The server covers the resource types listed above rather than presenting every OneUptime capability through MCP. Its tool set does not describe direct MCP operations for monitors, incidents, alerts, status pages, on-call schedules, logs, metrics, or traces.

Deletion is irreversible according to the tool descriptions, so agents should verify the target ID before calling a delete operation. Resource IDs are required for individual retrieval, updates, and deletion; list operations are the discovery path when an ID is not already known.