Muerte Cloud/Docs
Get Started
DocsOperationsAgents and MCP

Agents and MCP

The console works through a browser and through an AI assistant. Connect it once, then manage infrastructure in plain language: “show me why the deploy failed”, “restart the service”, “back up the volume before the update”.

The connection uses the open MCP standard (Model Context Protocol), supported by modern AI assistants and code editors.

What the agent can do#

FieldDescription
ObservationServices and projects, statuses, deploy history, build and application logs, CPU and memory metrics, domains.
Environment variablesView, add, change and delete variables.
DatabasesRetrieve connection parameters for managed databases.
OperationsStart, stop, restart and redeploy, change build type and port, upload a new archive.
CreationNew services and databases, volumes, backup schedules, scheduled jobs.
RecoveryList rollback points and roll a service back to a chosen build.
DeletionDelete services, volumes, schedules and jobs.

The agent sees only your services and acts strictly on your behalf.

Connecting an assistant#

  1. 1
    Configure permissions

    In console.muerte.cloud open Settings → MCP and enable only the permission groups you actually need.

  2. 2
    Add the MCP server

    In your assistant's settings add a new MCP server pointing at https://console.muerte.cloud/mcp. Most clients accept the configuration below; GUI assistants usually just need Add connector / Add MCP server and the same URL.

  3. 3
    Confirm sign-in
    On first use the assistant opens the console login page. Sign in, check the name of the application requesting access, and press Allow. The assistant receives permission-scoped access on your behalf; your password is never shared.
  4. 4
    Test the link
    Ask the assistant: “List my services.” You should get names, statuses and addresses back. If the list is empty but services exist, check you signed in with the same account.
mcp.json
json
{
  "mcpServers": {
    "muerte-cloud": {
      "type": "http",
      "url": "https://console.muerte.cloud/mcp"
    }
  }
}

Available permissions

FieldDescription
ReadServices and projects, statuses, deploys, logs, metrics, domains. Always on.
Read env variablesView variable values.
Write env variablesAdd, change and delete variables.
Database credentialsHost, port, user, password and connection string.
Operate and deployStart, stop, restart, redeploy, build type, port, archive upload.
Create services and databasesCreate new resources.
DeleteDelete services and related resources.

If a permission is off, the matching action answers with forbidden and services stay untouched. Permissions can be changed at any moment — no reconnection needed.

Recommended starting set
Read + Operate and deploy. Enable deletion and database credentials only while you actually need them.

Managing sessions#

Every active assistant connection is listed under Settings → Sessions, where you can revoke one connection or all of them. After revocation the assistant stops working with the console until it signs in again. Revoke access if you connected an assistant on someone else's or a temporary device, the tool is no longer used, or you have any security doubt.

Example prompts#

  • “Which services are down right now?”
  • “Show the last 200 log lines of the api service.”
  • “Why did the site's last deploy fail?”
  • “Add LOG_LEVEL=debug to the worker service and redeploy it.”
  • “Back up the volume before the update.”
  • “Roll the service back to the previous successful build.”
  • “Create a scheduled job: clear the cache nightly at 04:00.”

Security#

  • The agent acts only within granted permissions — they are checked by the console on every action, not by the assistant.
  • Secrets and passwords never reach the model unless reading them is enabled.
  • Access can be narrowed under MCP or fully revoked under Sessions at any time.
  • Before irreversible operations (deletion, rollback) ask the assistant to show its plan and confirm consciously.

FAQ#

Do I need to install anything?

No. The connection uses the console URL; no local components are required.

Can I connect several assistants?

Yes. Each connection shows up separately under Sessions and is revoked independently.

Will the agent see other people's projects?

No. Access is limited to your account.

The assistant answers “forbidden”?

The required permission is off. Enable it in Settings → MCP and retry.

The assistant answers “unavailable”?

The action is temporarily unavailable — for example the service is stopped and there are no logs for the current run. Check the service state and retry.

Previous
← Notifications