x=hub

your toolset

    build deployment
    sign in

    Acronis MCP

    mcpother
    io.github.Servosity/acronis-mcp · v0.1.6
    deploy just this

    The first real CLI for the Acronis Cyber Protect Cloud platform - every tenant, agent, and usage

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # once, as root:
    docker build -t mcp-local/acronis:latest https://github.com/servosity/msp-skills.git#:skills/acronis
    
    #!/usr/bin/env bash
    # acronis (io.github.Servosity/acronis-mcp), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-acronis.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-acronis -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp-local/acronis:latest
    
    [Unit]
    Description=MCP server acronis (toolset my-agent), generated by Hub
    After=network-online.target docker.service
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    SupplementaryGroups=docker
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/acronis
    WorkingDirectory=/var/lib/mcp/acronis
    ExecStart=/opt/mcp/my-agent/bin/acronis.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/acronis
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    docker build -t acronis https://github.com/servosity/msp-skills.git#:skills/acronis
    docker run --rm -p 127.0.0.1:8101:8000 -e ACRONIS_BASE_URL -e ACRONIS_BEARER_AUTH -e ACRONIS_CLIENT_ID -e ACRONIS_CLIENT_SECRET -e ACRONIS_DATACENTER acronis
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T06:55:06+00:00).
    # Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
    #   cp .env.example .env    # fill the ${VAR}s
    #   docker compose up -d && bash smoke.sh
    # Remote servers are not here: clients reach them directly (see clients/).
    name: mcp-my-agent
    services:
      acronis:
        build:
          context: https://github.com/servosity/msp-skills.git#:skills/acronis
        ports:
        - 127.0.0.1:8101:8000
        restart: unless-stopped
        x-note: 'CHANGE_ME: built from the repository''s Dockerfile, assuming it serves streamable HTTP at
          :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.'
        environment:
          ACRONIS_BASE_URL: ${ACRONIS_BASE_URL}
          ACRONIS_BEARER_AUTH: ${ACRONIS_BEARER_AUTH}
          ACRONIS_CLIENT_ID: ${ACRONIS_CLIENT_ID}
          ACRONIS_CLIENT_SECRET: ${ACRONIS_CLIENT_SECRET}
          ACRONIS_DATACENTER: ${ACRONIS_DATACENTER}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T06:55:06+00:00).
    #   kubectl create namespace mcp
    #   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
    #   kubectl apply -f kubernetes.yaml
    # Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
    # with auth in front before exposing any of them.
    apiVersion: v1
    kind: Namespace
    metadata:
      name: mcp
    ---
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: acronis
      namespace: mcp
      labels: &id001
        app: acronis
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: acronis
            image: CHANGE_ME
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: ACRONIS_BASE_URL
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ACRONIS_BASE_URL
            - name: ACRONIS_BEARER_AUTH
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ACRONIS_BEARER_AUTH
            - name: ACRONIS_CLIENT_ID
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ACRONIS_CLIENT_ID
            - name: ACRONIS_CLIENT_SECRET
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ACRONIS_CLIENT_SECRET
            - name: ACRONIS_DATACENTER
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ACRONIS_DATACENTER
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: acronis
      namespace: mcp
    spec:
      selector:
        app: acronis
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T06:55:06+00:00).
    # Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
    # Each server under `servers` is one Deployment + Service; the keys after it configure
    # upstream charts a worker verified.
    servers:
      acronis:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: acronis
          image: CHANGE_ME
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: ACRONIS_BASE_URL
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ACRONIS_BASE_URL
          - name: ACRONIS_BEARER_AUTH
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ACRONIS_BEARER_AUTH
          - name: ACRONIS_CLIENT_ID
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ACRONIS_CLIENT_ID
          - name: ACRONIS_CLIENT_SECRET
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ACRONIS_CLIENT_SECRET
          - name: ACRONIS_DATACENTER
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ACRONIS_DATACENTER
    
    # helm install my-agent helm/my-agent -n mcp
    

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb

    The form opens with CHANGE_ME for each value you supply: ACRONIS_BASE_URL, ACRONIS_BEARER_AUTH, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_DATACENTER. Fill them in before you deploy.

    Koyeb builds the repository's Dockerfile from branch main; change the branch in the form if the default one has another name.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    cloud run

    Cloud Shell clones the repository, builds its Dockerfile and deploys it to Cloud Run.

    Cloud Run sends requests to $PORT (8080); the recipe expects :8000, so the server has to read PORT, or set the container port on the service afterwards.

    Set ACRONIS_BASE_URL, ACRONIS_BEARER_AUTH, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_DATACENTER on the service afterwards: the button asks only for what the repository's own app.json lists.

    connect to it

    copy what your client needs
    {
      "mcpServers": {
        "acronis": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add acronis -- CHANGE_ME
    
    {
      "mcpServers": {
        "acronis": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    {
      "servers": {
        "acronis": {
          "type": "stdio",
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.Servosity/acronis-mcp
    
    • not probed yet: tools unpinned, ingest lists them
    • no recipe for target 'local': fill the files by hand

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.