SimpleBackupsSimpleBackups
Private beta·SimpleBackups MCP server

Your backups,
now answer back.

Connect SimpleBackups to Claude, Cursor, Codex, or any MCP client. Manage, check, investigate, and automate - without leaving the conversation.

// manage·check·investigate·automate //

Join the private beta→See it in action
Read the docs/API reference
// same outcome

0 clicks→1 sentence.

Pick a task. Watch both sides race. Same answer, different speed.

Ssimplebackups.com/dashboard
Backups
action log
  1. Find the broken one
    ▶
    Open Backups list
  2. 2
    Apply filter— status: failed
  3. 3
    Sort by name
  4. 4
    Click— mysql-orders-staging
  5. Diagnose
    5
    Switch to Logs tab
  6. 6
    Expand last failed run
  7. 7
    Read SSH timeout error
  8. 8
    Open server— in another tab
  9. 9
    Check other backups— on same server
  10. 10
    Confirm: only this one fails
  11. Retry
    11
    Back to backup
  12. 12
    Switch to Runs tab
  13. 13
    Click Trigger now
  14. 14
    Confirm dialog
Clicks0/ 14
Time0:00
in progress
Cclaude·simplebackups MCP
M
Why did mysql-orders-staging fail?
Sentences1
Time0:00
in progress

Run this 3× a week → ~13 hours back per quarter.

// nine real workflows

From the dashboard, into the conversation.

Nine workflows, grouped by what they ask of the agent. Pick one from the index and watch it run.

scenario_restore
01

Pull prod, restore local.

M
Pull the latest postgres-xyz backup and prep a restore as postgres-xyz_local.
✓list-backups(name:postgres-xyz)
✓restore-prep(backup_id:b_8f12 target:local)
C
Most recent run: 47 min ago, 312 MB. Prepared restore for localhost:5432. Expected: 11 tables, 1.2M rows. Instructions ready. Run them now?
A Confluence page in one sentence.
← → to navigate
// get started

No time to click around?
Start asking instead.

// claude · cursor · codex · any MCP client

Private beta — limited spots. We'll be in touch within a few days.

Join the private beta→Read the docs
Building against the MCP server? See the API reference →