AI setup

Let your AI set up your backups

Connect Claude Code or Cursor to VPS Snaps. It looks at your server, proposes a backup plan, and once you agree installs the agent and every job.

Example session

› Set up VPS Snaps backups for this server.

● get_account     Standard plan: 15 servers, 20 jobs, every 12 hours
● list_storage    "Primary backups" (Amazon S3)
● Looked around   PostgreSQL "shop", Docker volume uploads_data,
                  /var/www/shop

  Proposed plan:
    shop database   every 12 hours, keep 14 days
    uploads_data    daily, keep 14 days
    /var/www/shop   daily, keep 14 days
  Go ahead?

› Yes.

● create_agent        install command shown, run with your OK
● get_agent           CONNECTED
● create_backup_job   ×3
● run_backup_job      ×3, all three succeeded

What you do, and what it does

Three steps are yours, done once. The rest happens in your terminal. API access is on the Standard plan and up.

You

1
Sign up and connect storage
Your own S3-compatible bucket or Google Drive, connected in the dashboard. Your assistant never sees those keys.
2
Create an API key
Settings → API keys, with Full access. Name it after the machine or the assistant, and revoke it whenever you like.
3
Add VPS Snaps to your assistant
One command in Claude Code, or a few lines of config in Cursor. Then paste the prompt below.

Your assistant

1
Reads your plan and storage
So it proposes what your plan allows, and stops to send you to the dashboard if no storage is connected yet.
2
Looks at the machine
Databases and how to reach them, Docker volumes, web roots. It is in your terminal already, so it can look for itself.
3
Proposes a plan and waits
What to back up, how often and for how long. Nothing is created until you say yes.
4
Sets it up and proves it
Installs the agent once you have seen the command, creates the jobs, runs each one once and shows you the results.

Connect it

Make a key with Full access in Settings → API keys first. The key goes in place of vps_YOUR_KEY.

Claude Code

claude mcp add --transport http vpssnaps https://vpssnaps.com/api/mcp --header "Authorization: Bearer vps_YOUR_KEY"

Cursor: .cursor/mcp.json

{
  "mcpServers": {
    "vpssnaps": {
      "url": "https://vpssnaps.com/api/mcp",
      "headers": { "Authorization": "Bearer vps_YOUR_KEY" }
    }
  }
}

Then paste this prompt

Set up VPS Snaps backups for this server using the vpssnaps MCP tools.

1. Check my plan and limits (get_account) and my storage (list_storage). If I have no storage connected, tell me to add it in the VPS Snaps dashboard and wait. Never ask me for storage keys or cloud tokens.
2. Look at what is on this machine: databases and how to reach them, Docker volumes (docker volume ls), and web roots or app directories worth keeping.
3. Propose a backup plan that fits my plan's limits: what to back up, how often, and how long to keep it. Wait for my OK.
4. Create an agent for this machine with the paths and options the plan needs. Show me the install command before you run it.
5. Once the agent reports CONNECTED, create the backup jobs, run each one once, and show me how each first run went.

The same instructions, written for an assistant to read, are at /ai-setup.md.

What it can do, and what it cannot

Ten tools, all of them about setting backups up and checking on them.

get_accountPlan and limits
list_storageStorage destinations
list_agentsAgents
create_agentCreate an agent
get_agentAgent status
list_backup_jobsBackup jobs
create_backup_jobCreate a backup job
run_backup_jobRun a backup now
list_backup_runsRecent runs
get_backup_runOne run, with its log

No storage keys, cloud tokens or SSH keys

No tool takes one. Storage is connected by you, in the dashboard. A database password is the one secret it handles, for a database on the machine it is already working on.

Nothing deleted, nothing restored

It can create, list, run and read. Deleting, editing and restoring stay in the dashboard, with a person.

Everything it makes is in your audit log

Each agent, job, server or storage destination created through the API is recorded, under the key's name.

Your plan's limits, exactly

The same checks as the dashboard: servers, jobs, job types, schedules and retention. A refusal says which limit, so the assistant can tell you.

Or script it

The same key works on the REST API. Endpoints marked Full need a key with Full access.

GET	/api/v1/account	Plan, limits, usage, and what this key may do
GET	/api/v1/storage-destinations	Storage destinations, never with their keys
POST	/api/v1/storage-destinations	Connect an S3-compatible bucketFull
GET	/api/v1/agents	Agents and whether each is connected
POST	/api/v1/agents	Create an agent; returns its install command onceFull
GET	/api/v1/agents/{id}	One agent's status
GET	/api/v1/servers	Servers reached over SSH
POST	/api/v1/servers	Add a server reached over SSHFull
GET	/api/v1/backup-jobs	Every backup job
POST	/api/v1/backup-jobs	Create a backup job, with the dashboard's plan checksFull
GET	/api/v1/backup-jobs/{id}	One job with its recent runs
POST	/api/v1/backup-jobs/{id}/run	Start a backup now
GET	/api/v1/backup-runs	Recent runs, filterable
GET	/api/v1/backup-runs/{id}	One run, with its log

Try it

curl -s https://vpssnaps.com/api/v1/account \
  -H "Authorization: Bearer vps_YOUR_KEY"

Creating is limited to 20 requests a minute per key and reading to 120. Every agent, job, server or storage destination a key creates is in your audit log.

FAQs

Can’t find the answer you’re looking for? Reach out to our support team.

Which AI assistants work with it?

Any MCP client that can connect to a remote server over HTTP and send an Authorization header: Claude Code, Cursor and others. The server is at https://vpssnaps.com/api/mcp. Clients that can only connect with OAuth, such as claude.ai's web connectors, cannot use it yet.

Which plans include it?

API keys, the REST API and the MCP server are on the Standard plan and up. A key stops working if the workspace moves to a plan without API access, and starts again if it moves back.

What can an API key do?

A key with Full access can create agents, storage destinations, servers and backup jobs, start backups and read everything back. A Read and run key can list jobs and runs and start a backup, and nothing else. Either can be revoked in Settings at any time, and anything using it stops at once.

Does the assistant see my passwords?

It never sees storage keys, cloud tokens or SSH keys: no tool accepts one. It sees the agent's token, inside the install command it runs for you, and a database password if it sets up a database backup. That database is on the machine it is already working on.

Can I do this without an AI?

Yes. The same key works on the REST API below, from a script or curl, and everything can be done in the dashboard as well.

Back up the server you are working on, from where you are working.

Sign up, connect a bucket, and make a key on the Standard plan or above. Your assistant does the rest, and asks before it does anything.

No credit card required. Cancel anytime.