Blog

Ask your AI client about your backups: BackupLatte MCP

· 3 min read

The BackupLatte cup connects over MCP to a chat answering which backups need attention.

A backup only helps if somebody notices when it stops working. A failed run shows up as an email or a red badge on a dashboard, and both are easy to miss in a busy week.

Now you can ask instead. BackupLatte has an MCP server: connect a compatible AI client to your account and ask it which Linear and ClickUp workspaces need attention, what the last backup contained, or whether you can run one now.

What it can do

MCP, the Model Context Protocol, is how AI clients connect to outside tools. Through BackupLatte's server, a client can:

Things to try

What it can't do, on purpose

We've written before about giving AI agents write access to the tools a team depends on. So we kept this one narrow.

A client can't start a restore, download a snapshot, change settings or billing, connect or disconnect a workspace, or delete anything. Those stay in the BackupLatte app. The only thing it can change is the backup queue, and only if you allow it.

Running a backup works in two steps. By default, start_backup is a dry run: it checks that the workspace is connected, that no backup is already running and that your manual backup limit allows a new one, without queueing anything. A backup is queued only when the client explicitly asks with dryRun: false, and it counts toward the same limit as the Run backup now button: one manual backup per workspace every 24 hours.

Connect a client

You need a verified BackupLatte account and an active subscription on each integration you want to reach. MCP is included in every plan.

  1. In your AI client, add a remote MCP server over Streamable HTTP with the URL https://app.backuplatte.com/api/mcp.
  2. The client opens your browser. Sign in to BackupLatte, or create an account, and confirm your email if asked.
  3. Check the consent screen: the client's name, the integrations it will see and the permissions it asks for. Leave Allow manual backups unticked if you want read-only access.
  4. Choose Allow access, go back to the client and ask which of your workspaces needs attention.

The client never sees your BackupLatte password. It signs in through OAuth and gets access to your account's workspaces on integrations with an active subscription. The MCP guide has the details.

See what it did, and switch it off

MCP settings in the app list every connected client, its permissions and its recent activity. Revoke access ends a client's access straight away; to use it again, connect from the client once more.

The activity log keeps 90 days of tool names and outcomes. It doesn't store what the client asked for or the backup data it got back. Whatever the client received before you revoked it stays with the client, so treat it like any other app you give access to.

If you haven't set up backups yet, start with our guides for Linear and ClickUp.

More from the blog