Changelog

Through the Model Context Protocol (MCP), your AI assistant works with LIVCK directly. You write, for example, “Schedule maintenance tonight from 2 to 4 am for every service tagged db and announce it”. The assistant prepares the maintenance and shows you the text, times and recipients.

It opens incidents and writes their updates, schedules maintenance, creates or edits services and looks for the cause of an outage. Depending on the connection's rights and scope, status pages, on-call, SLA, activity and support tickets come on top.

You create the connection under AI & MCP in your organization's settings. For 30 clients, among them Claude Code, Cursor, VS Code, OpenAI Codex, Gemini CLI, OpenCode and Claude Desktop, the console shows you the finished configuration. Reading is included on every plan, the free one too. Writing comes with Solo and up.

Connect an AI assistant

Anything that reaches customers, wakes someone up, silences alerting or deletes something is shown as a preview first: recipients, texts per language, times and what will be lost. It only runs once you confirm. If someone on your team changes the text after your preview, LIVCK does nothing and the assistant has to ask you again.

For clients that do not ask on their own, choose Approve with a click in the browser. The action then waits under Approvals until you approve it.

Each connection gets No access, Read, Write or Delete per area. Three switches decide what reaches the outside: Notify customers, Wake on-call and Silence or change alerting. A connection never has more rights than the person who created it. Its token only works for MCP, not for the API.

New entries in Activity now show how a change was made: in the browser on a desktop or phone, through the API with the token's name, or by an AI assistant with its client's logo, for example “via Claude Code”. With the Channel filter you can show only the changes made by AI assistants.

With GET, POST and DELETE /v1/enrollment-keys you manage keys. The key itself only appears in the response when you create it, together with the ready-made install command. Every key lists the server agents that enrolled with it.

Every server agent has the agent block in the API with its state, host data, update settings and the key it enrolled with. GET /v1/services/{id}/agent-metrics returns the current values, /agent-metrics/history the history.

Enrollment tokens now carry real tags of your organization. Server may add its own tags decides whether tags from the install command are added. A token's tag may also fill a status page group.

Open enrollment tokens

When you share an invitation in Slack, Teams or WhatsApp, the preview shows the organization's name and who is inviting.

When measurement data is briefly unavailable, /checks and the server agent metrics answer with empty values instead of an error.

Your status page now follows the setting on each visitor's device. If a phone or computer is set to dark, the status page appears dark too. When the device changes its setting, the open page changes with it. This applies to all status pages from now on. There is nothing to set up.

Through the gear icon on the status page, visitors pick Light, Dark or System themselves. The browser remembers the choice. With System, the page follows the device again.

In the Branding tab you set System, Light or Dark for each status page. With Visitors can switch turned off, everyone sees exactly that appearance and the switch on the status page is hidden.

Open status pages

Status pages have two new fields in the API: appearance (system, light or dark) and allow_appearance_switch. You set both with PATCH /v1/statuspages/{id}.

Your primary colour now takes effect on the status page and stays readable in light and dark mode. Where the contrast with the background falls short, we adjust its brightness.

Every status page now has a preview image of its own. It shows your page's name, logo and primary colour. At the bottom is the address from the shared link, followed by the current status. If someone shares a link on your own domain, the image shows that domain too. While everything runs, the image glows in your primary colour, otherwise in the colour of the status.

Every incident and every maintenance gets an image of its own with title, time and affected components. There is nothing to set up.

On the Free plan the image carries a small LIVCK logo at the bottom right, just like the footer of your status page.

In the SEO tab of your status page's settings you decide what search engines and link previews show:

• title, description and the subtitle in the image, per language of your status page
• background of the image: automatic, light or dark
• whether previews show the current status
• whether incidents and maintenance get images of their own
• whether search engines may list the page

The tab shows the image as it appears when shared. Platforms often keep previews for hours, messengers keep them in old messages for good. If a shared link should never show an outdated status, turn off the status in previews.

Status pages now have a seo field in the API with the same settings as the tab. With PATCH /v1/statuspages/{id}, seo replaces all of them at once. Whatever you leave out goes back to its default, and "seo": {} resets everything. If you leave out seo entirely, everything stays as it is.

Your organisation's settings now have a time zone. The preview images of incidents and maintenance give start and end in it. The default is Europe/Berlin.

Status pages with a password or an email whitelist no longer appear in search engines. Their preview images show only name, logo and address, never a status. Search engines also no longer pick up the links subscribers use to confirm or manage their subscription.

The time zone picker now groups zones by continent, with Europe at the top and cities in alphabetical order. This applies wherever you pick a time zone: in the organisation, for heartbeats and for SLA objectives.

Saving a status page reset the logo size to Medium. It now stays as you set it. The form also uploaded a newly chosen logo again on every further save. That is fixed too.

A token that deletes a service with delete_orphaned_incidents or delete_orphaned_maintenances now also needs Delete Incidents or Delete Maintenances respectively, otherwise the API answers 403. A token whose creator is limited to access areas now links incidents and maintenance only to services and status pages inside those areas. If your script uses either parameter, give its token the matching permission.

With livck/cloud-php you drive LIVCK Cloud from PHP without building JSON by hand. Services come from a typed builder, every error arrives as an exception of its own, and the client pages through lists itself. If a connection drops, it repeats the request with the same Idempotency-Key, and nothing is created twice. livck/cloud-laravel adds configuration, a facade, several connections and a fake for tests. Both packages are MIT-licensed.

• composer require livck/cloud-php
• composer require livck/cloud-laravel

Guides: PHP SDK and Laravel

A service's tags field now takes names or ids, in any mix: tags: ["customer:4711", "env=prod"]. The API creates a new name along with the service. Only an entry that looks like a tag id (21 characters with at least one uppercase letter) has to be an existing tag.

GET /v1/statuspages?slug=customer-4711 returns exactly that page or an empty list. Every status page now gives its public address in url, and every component the status visitors see in effective_status.

When a service or a custom domain hits a limit of your plan, the 403 response now carries upsell with the limit concerned, plus limit and usage. A script can tell a full quota from missing permissions that way.

The API's error messages are now always in English, also for organisations with German content. Accept-Language only decides the language of content, such as incident titles.

GET /v1/services?tag= with an empty value now returns an empty list instead of every service. A script whose variable came out empty never gets all services by accident.

statuspage_id was empty on custom domains. It now names the domain's status page.

Editing a status page with email_whitelist: null ended in a 500. null now counts as an empty list.

An oversized request got an HTML page back. The API now answers 413 with an error message in JSON.

On roadmap.livck.cloud you can see what we are working on right now, what comes next and what is done. With your LIVCK account you can:

• vote on topics
• follow topics
• join the discussion
• submit ideas of your own

A submission is first seen only by you, your organisation and us. If it appears on the board, it does so in our wording and without your name.

Our Discord bot brings your status page into a Discord channel. Until now that worked only with Self-Hosted; since 22 September it also works with status pages from LIVCK Cloud. To set it up:

1. Invite the bot to your Discord server.
2. Run /livck subscribe in the channel you want and paste the address of your status page. Cloud or Self-Hosted, the bot works that out itself.

Incidents and maintenance then appear as threads of their own.

Three new endpoints return everything around a service:

• GET /v1/services/{id}/incidents: its incidents
• GET /v1/services/{id}/maintenances: its maintenance
• GET /v1/services/{id}/checks: its check results with location, status, HTTP code, error and timings

That way the API also tells you why a service was unreachable. /v1/incidents and /v1/maintenances can also be narrowed to several services with service_ids.

Write requests (POST) accept an optional Idempotency-Key header. If the response to a successful request never arrives, for example because of a timeout, just repeat it with the same key. You get the original response back, and nothing is created twice. The only exception is uploading logos and favicons.

• GET /v1/tags now filters by label and key.
• POST /v1/tags/ensure creates a tag or returns the existing one.

No more paging through a list to find a tag.

If part of creating a service through the API fails, such as setting its tags, no half-created service is left behind any more. A second attempt therefore creates no duplicate.

Create, change and delete — the page itself and every component, plus appearance, access control, logo and favicon.

A status page no longer has to be rebuilt by hand in every environment.

Create tags, assign services, fill status page groups from a tag. New services then land in the right group on their own.

Add and verify without opening the console.

A status page's charts can be set through the API too.

Translated fields also come back with every language, so writing them back loses no language you did not request.

What the console rejects, the API rejects too.