Integration

SimpleBackups integration

SimpleBackups schedules and runs server file and database backups (MySQL, PostgreSQL, MongoDB) to cloud storage. Create, update, run, pause, resume and delete backup jobs, get signed download links for backup files, add, validate and remove servers, list storages, read each backup's runs and next scheduled dates, and list or switch teams. Not exposed: the encryption passphrase links of encrypted backups, the per-backup trigger URL (it embeds a token), restore commands and dashboard download URLs, and the job activity, activity report and schedule statistics routes, whose response shape SimpleBackups does not document. Authentication is an API token created in SimpleBackups Settings, API, sent as a Bearer token; requests are limited to 60 per minute.

Connect SimpleBackups How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with SimpleBackups

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.

List, 4 operations

list_backupsList backupsGETLists the backup jobs of the current team, optionally filtered by id, name, status, type, server or storage.
list_serversList serversGETLists the servers added to the current team.
list_storagesList storagesGETLists the storages (cloud storage providers) of the current team, optionally filtered by name or status. Each id is a storage_id for create_backup.
list_teamsList teamsGETLists the teams the account belongs to. Use switch_team to choose which team later calls act on.

Backup, 2 operations

delete_backupDelete backupPOSTDeletes a backup job. Backup copies already on the storage are kept. HTTP 409 while the backup is in progress (initiated or running).
run_backupRun backupGETStarts a backup job now. Returns the new run in data (status initiated). HTTP 409 means the backup is already in progress.

Download link, 2 operations

get_backup_download_linkGet backup download linkGETReturns signed download links for the last successful run of a backup job: data.file.signed_link and data.db.signed_link (a full backup has both). Links expire after 300 seconds.
get_backup_log_download_linkGet backup log download linkGETReturns signed download links for one specific run (log) of a backup job: data.file.signed_link and data.db.signed_link. Links expire after 300 seconds. Log ids come from the logs of list_resource_activity.

Add, 1 operation

add_serverAdd serverPOSTAdds a server. With connection_type password send the SSH password; with ssh or agent, run the returned data.install_command on the server right away, then call validate_server_connection.

Create, 1 operation

create_backupCreate backupPOSTCreates a backup job for an existing server and storage. A schedule other than on-demand makes SimpleBackups run it automatically. Returns the job in data (id for run_backup).

Current, 1 operation

get_current_teamGet current teamGETReturns the team the API token currently acts on. HTTP 404 when no team is set yet: call switch_team first.

Pause, 1 operation

pause_backupPause backupPATCHPauses a backup job's automatic schedule. It can still be started on demand with run_backup; resume_backup restores the schedule.

Resource, 1 operation

list_resource_activityList resource activityGETLists backups, snapshots or cloud syncs with their storage, server, next five scheduled runs and the runs (logs) of the period (default the last month).

Resume, 1 operation

resume_backupResume backupPATCHResumes a paused backup job's automatic schedule.

Server, 1 operation

remove_serverRemove serverPOSTRemoves a server from SimpleBackups and revokes its access to it. The removal is queued and may take a couple of minutes.

Switch, 1 operation

switch_teamSwitch teamPATCHSwitches the account to another team it belongs to; every later request then acts on that team. Answers 204 with no body.

Update, 1 operation

update_backupUpdate backupPATCHUpdates a backup job. name, schedule and retention are required on every call: read the current values first (list_backups with filters id) and send them back with the change. storage_id, server_id and type cannot be changed.

Validate connection, 1 operation

validate_server_connectionValidate server connectionGETChecks that SimpleBackups can connect to a server, so it is ready for backups. data.status is true when connected; data.message explains a failure.

Use SimpleBackups from Claude Code, Cursor or Codex

Connect SimpleBackups in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SimpleBackups 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 SimpleBackups

Create your workspace
Sign up free. Nothing to install.
Connect SimpleBackups once
Add your SimpleBackups 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.