Connect AI assistants

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.