MCP · CLI · API
Run your projects from an AI agent
Add one config entry to Claude Code, Cursor, Codex or another client. From then on the model sees your projects, reads build logs, deploys and rolls back.
What is MCP?
The Model Context Protocol is an open standard AI clients use to call other services’ tools. Livops is an MCP server.
One URL
Streamable HTTP, signed in through the browser or with a Bearer token. Or stdio through the CLI.
Most of the cabinet
Projects, deploys, databases, domains, files, the team and billing. Every tool is marked as read-only or as one that changes things.
Your permissions
The model can do what the token can. Nothing more.
Connect in three steps
In most clients you just add the address: the browser opens, you pick a team and allow access. The others need an API token from the team settings.
- 1Add the address to your AI client
- 2Allow access in the browser, or paste an API token
- 3Ask about your project
Through the browser
Then in Claude Code: /mcp → livops → Authenticate. The browser opens.
claude mcp add --transport http livops https://livops.uz/api/mcpOr with an API token
One command in the terminal.
claude mcp add --transport http livops https://livops.uz/api/mcp \
--header "Authorization: Bearer lvp_xxx"Through the browser
Just the address. Cursor asks you to sign in in the browser on first connect.
{
"mcpServers": {
"livops": {
"url": "https://livops.uz/api/mcp"
}
}
}Or with an API token
~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one.
{
"mcpServers": {
"livops": {
"url": "https://livops.uz/api/mcp",
"headers": {
"Authorization": "Bearer lvp_xxx"
}
}
}
}Through the browser
Not in the Connectors Directory. Customize → Connectors → Add custom connector, and paste this address. The browser opens on first connect.
https://livops.uz/api/mcpOr with an API token
Or the CLI: Settings → Developer → Edit Config. Install the livops CLI first; it talks over stdio.
{
"mcpServers": {
"livops": {
"command": "livops",
"args": [
"mcp"
],
"env": {
"LIVOPS_TOKEN": "lvp_xxx"
}
}
}
}Through the browser
login opens the browser; after you allow it, the key renews itself.
codex mcp add livops --url https://livops.uz/api/mcp
codex mcp login livopsOr with an API token
The token is read from the environment and never lands in config.toml.
export LIVOPS_TOKEN=lvp_xxx
codex mcp add livops --url https://livops.uz/api/mcp \
--bearer-token-env-var LIVOPS_TOKENThrough the browser
.mcp.json in the workspace root (or ~/.copilot/mcp-config.json for every workspace). Pick the Copilot harness in chat and complete sign-in when asked; the browser opens.
{
"mcpServers": {
"livops": {
"type": "http",
"url": "https://livops.uz/api/mcp",
"tools": [
"*"
]
}
}
}Or with an API token
.mcp.json in the workspace root. The token is read from LIVOPS_TOKEN; set it before VS Code starts.
{
"mcpServers": {
"livops": {
"type": "http",
"url": "https://livops.uz/api/mcp",
"headers": {
"Authorization": "Bearer ${LIVOPS_TOKEN}"
},
"tools": [
"*"
]
}
}
}mcp_config.json, opened from the MCP settings in Cascade. Note serverUrl, not url.
{
"mcpServers": {
"livops": {
"serverUrl": "https://livops.uz/api/mcp",
"headers": {
"Authorization": "Bearer lvp_xxx"
}
}
}
}Through the browser
Then in Gemini CLI: /mcp auth livops.
gemini mcp add --transport http livops https://livops.uz/api/mcpOr with an API token
Writes the entry to the project's .gemini/settings.json, or ~/.gemini/settings.json.
gemini mcp add --transport http \
--header "Authorization: Bearer lvp_xxx" livops https://livops.uz/api/mcpThrough the browser
With no header set, Zed offers to sign in through the browser.
{
"context_servers": {
"livops": {
"url": "https://livops.uz/api/mcp"
}
}
}Or with an API token
Add it to Zed's settings.json.
{
"context_servers": {
"livops": {
"url": "https://livops.uz/api/mcp",
"headers": {
"Authorization": "Bearer lvp_xxx"
}
}
}
}In the Cline panel: MCP Servers → Configure → Configure MCP Servers.
{
"mcpServers": {
"livops": {
"type": "streamableHttp",
"url": "https://livops.uz/api/mcp",
"headers": {
"Authorization": "Bearer lvp_xxx"
}
}
}
}Client not listed? Any MCP client that speaks Streamable HTTP and supports MCP OAuth or an Authorization header works. If yours can’t, run livops mcp from the CLI over stdio.
What it can do
The ones you will reach for most, named as the server names them. Every tool is in the MCP docs.
Read-only · 10
list_projectsyour team’s projects, status and URLget_projectone project: status, service, domains, databaseslist_deploysa project’s deploys, newest firstget_deploy_logdeploy status and the tail of the build logget_logsthe tail of the running service’s loglist_variablesvariable names, never valueslist_databasesattached databases, never passwordslist_domainscustom domains and the DNS targetget_metricsCPU, memory and traffic for 1h, 24h or 7dexplain_failurethe assistant explains why a build failed
Actions · 5
deployredeploy from the current sourcerollbackroll back to an earlier deployrestartrestart the running serviceset_variableadd or change one variableadd_domainattach a custom domain
Where the limits are
A token can’t delete, pay or read passwords
An lvp_ API token deploys and reads. Deleting, database passwords, bucket keys and top-ups work only when the client is connected through the browser, as you.
Changes can ask you first
Tools that change data are marked destructive, so your client can ask before they run. Keep those confirmations on.
Variable values stay out
Listing variables gives names and which are secret, never the values.
Leave its team
A token, like an app connected through the browser, belongs to one team and one person.
Write as a viewer
A token, or an app connected by someone with the viewer role, can’t change anything.
Skip the limits
Every call goes through the regular API and is rate limited. Give the AI its own token and revoke it when you’re done.
Try asking
- “Why did the last shop-api deploy fail?”
- “Which project used the most memory in the last 24 hours?”
- “Roll shop-web back to the previous version”
- “Set LOG_LEVEL=debug and show me the logs”
- “Attach shop.uz to shop-web. What do I put in DNS?”
- “Which of my projects are down right now?”
Get the CLI first
Claude Desktop needs it, and it’s handy in a terminal anyway.
curl -fsSL https://livops.uz/install.sh | sh
livops loginBuilt-in assistant
No MCP needed: the assistant lives in the cabinet and in Telegram
Nothing to install. When a build fails, the assistant reads the log and offers the fix as a button.
- A deploy you ask for starts at once; anything else that costs money waits for your press
- It never sees variable values
- It never deletes anything
- You can turn it off in settings