Arkame Backup

app.arkamePublished by arkame.appOfficial publisherv2.106.5Updated Oct 29, 2026

Backups of servers, Docker and Zimbra to your own S3. Restore by chat; changes need 2FA approval.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFiles & Storage

Overview

AI-generated overview

Remote MCP server that lets an assistant back up servers, Docker and Zimbra to your own S3 storage and restore them by chat.

What you can do
  • Back up servers, Docker environments and Zimbra mail to an S3 bucket you own
  • Restore backups through a chat request
  • Changes require two-factor approval before they take effect
  • No tool list is published, so the exact operations are not documented in the manifest
When to use it
Worth adding when you want an assistant to trigger or restore backups of servers, Docker hosts or Zimbra mail into your own S3 storage, with a human approval step for changes.
Requirements
Remote streamable HTTP endpoint at save.arkame.app; no local install. Authentication is required via OAuth or a Bearer token in the Authorization header from the Arkame panel. Your own S3 storage is needed for the backups.
Before you install
The server holds credentials that can back up and restore infrastructure, so treat the Authorization token as sensitive. Restore operations change data on your servers; the provider states changes need 2FA approval, but confirm this before relying on it. Backups are written to your own S3 bucket, so storage access and costs are yours.

Installation

In SourceWeft

  1. Open Arkame Backup in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.arkame%2Fbackup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "arkame-backup": {
      "type": "http",
      "url": "https://save.arkame.app/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v2.106.5LatestOct 29, 2026
  2. v2.104.2Oct 20, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.