Integration

Cachet integration

Cachet is a self-hosted status page. Publish and maintain the operational state of a service: components and the groups they are shown in, incidents with their timeline of updates, reusable incident templates, scheduled maintenance windows with their own updates, metrics and the data points plotted on them, and the subscribers notified when any of it changes. A read of the overall system status and of the running Cachet version is also exposed. The host is part of the credential because every install is its own deployment. Reads are public on an unprotected instance; every write needs an API key sent as a bearer token in the Authorization header.

Connect Cachet How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Cachet.Built from the 52 Cachet tools below, on the connection you add once.

What you can do with Cachet

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Update, 10 operations

create_incident_updateCreate incident updatePOSTCreate Incident Update.
create_schedule_updateCreate schedule updatePOSTCreate Schedule Update.
delete_incident_updateDelete incident updateDELETEDelete Incident Update.
delete_schedule_updateDelete schedule updateDELETEDelete Schedule Update.
get_incident_updateGet incident updateGETGet Incident Update.
get_schedule_updateGet schedule updateGETGet Schedule Update.
list_incident_updatesList incident updatesGETList Incident Updates.
list_schedule_updatesList schedule updatesGETList Schedule Updates.
update_incident_updateUpdate incident updatePUTUpdate Incident Update.
update_schedule_updateUpdate schedule updatePUTUpdate Schedule Update.

Component, 5 operations

create_componentCreate componentPOSTCreate Component.
delete_componentDelete componentDELETEDelete Component.
get_componentGet componentGETGet Component.
list_componentsList componentsGETList Components.
update_componentUpdate componentPUTUpdate Component.

Component group, 5 operations

create_component_groupCreate component groupPOSTCreate Component Group.
delete_component_groupDelete component groupDELETEDelete Component Group.
get_component_groupGet component groupGETGet Component Group.
list_component_groupsList component groupsGETList Component Groups.
update_component_groupUpdate component groupPUTUpdate Component Group.

Incident, 5 operations

create_incidentCreate incidentPOSTCreate Incident.
delete_incidentDelete incidentDELETEDelete Incident.
get_incidentGet incidentGETGet Incident.
list_incidentsList incidentsGETList Incidents.
update_incidentUpdate incidentPUTUpdate Incident.

Incident template, 5 operations

create_incident_templateCreate incident templatePOSTCreate Incident Template.
delete_incident_templateDelete incident templateDELETEDelete Incident Template.
get_incident_templateGet incident templateGETGet Incident Template.
list_incident_templatesList incident templatesGETList Incident Templates.
update_incident_templateUpdate incident templatePUTUpdate Incident Template.

Metric, 5 operations

create_metricCreate metricPOSTCreate Metric.
delete_metricDelete metricDELETEDelete Metric.
get_metricGet metricGETGet Metric.
list_metricsList metricsGETList Metrics.
update_metricUpdate metricPUTUpdate Metric.

Schedule, 5 operations

create_scheduleCreate schedulePOSTCreate Schedule.
delete_scheduleDelete scheduleDELETEDelete Schedule.
get_scheduleGet scheduleGETGet Schedule.
list_schedulesList schedulesGETList Schedules.
update_scheduleUpdate schedulePUTUpdate Schedule.

Subscriber, 5 operations

create_subscriberCreate subscriberPOSTCreate Subscriber.
delete_subscriberDelete subscriberDELETEDelete Subscriber.
get_subscriberGet subscriberGETGet Subscriber.
list_subscribersList subscribersGETList Subscribers.
update_subscriberUpdate subscriberPUTUpdate Subscriber.

Point, 4 operations

create_metric_pointCreate metric pointPOSTCreate Metric Point.
delete_metric_pointDelete metric pointDELETEDelete Metric Point.
get_metric_pointGet metric pointGETGet Metric Point.
list_metric_pointsList metric pointsGETList Metric Points.

Instance, 1 operation

ping_instancePing instanceGETChecks that the Cachet instance is reachable and answering.

System status, 1 operation

get_statusGet statusGETReads the overall status of the instance, the single worst state across every component.

Version, 1 operation

get_versionGet versionGETReads the Cachet version the instance is running.

Use Cachet from Claude Code, Cursor or Codex

Connect Cachet in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Cachet operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Cachet

Create your workspace
Sign up free. Nothing to install.
Connect Cachet once
Add your Cachet connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.