Spanning Cloud Backup
mcpotherio.github.wyre-technology/spanning-mcp · v1.1.3
MCP server for Spanning Cloud Backup — M365/GWS/Salesforce backups, restores, audit.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
#!/usr/bin/env bash
# spanning (io.github.wyre-technology/spanning-mcp), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-spanning.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-spanning -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env ghcr.io/wyre-technology/spanning-mcp:v1.1.3
[Unit]
Description=MCP server spanning (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/spanning
WorkingDirectory=/var/lib/mcp/spanning
ExecStart=/opt/mcp/my-agent/bin/spanning.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/spanning
[Install]
WantedBy=multi-user.target
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
docker run --rm -p 127.0.0.1:8101:8000 -e SPANNING_PLATFORM -e SPANNING_ADMIN_EMAIL -e SPANNING_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/spanning-mcp:v1.1.3
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T06:04:22+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:
spanning:
image: ghcr.io/wyre-technology/spanning-mcp:v1.1.3
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
instead.'
environment:
SPANNING_PLATFORM: ${SPANNING_PLATFORM}
SPANNING_ADMIN_EMAIL: ${SPANNING_ADMIN_EMAIL}
SPANNING_API_TOKEN: ${SPANNING_API_TOKEN}
MCP_TRANSPORT: ${MCP_TRANSPORT}
AUTH_MODE: ${AUTH_MODE}
LOG_LEVEL: ${LOG_LEVEL}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T06:04:22+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: spanning
namespace: mcp
labels: &id001
app: spanning
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: spanning
image: ghcr.io/wyre-technology/spanning-mcp:v1.1.3
ports:
- containerPort: 8000
name: http
env:
- name: SPANNING_PLATFORM
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SPANNING_PLATFORM
- name: SPANNING_ADMIN_EMAIL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SPANNING_ADMIN_EMAIL
- name: SPANNING_API_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SPANNING_API_TOKEN
- name: MCP_TRANSPORT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MCP_TRANSPORT
- name: AUTH_MODE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: AUTH_MODE
- name: LOG_LEVEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: LOG_LEVEL
---
apiVersion: v1
kind: Service
metadata:
name: spanning
namespace: mcp
spec:
selector:
app: spanning
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T06:04:22+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:
spanning:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: spanning
image: ghcr.io/wyre-technology/spanning-mcp:v1.1.3
ports:
- containerPort: 8000
name: http
env:
- name: SPANNING_PLATFORM
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SPANNING_PLATFORM
- name: SPANNING_ADMIN_EMAIL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SPANNING_ADMIN_EMAIL
- name: SPANNING_API_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SPANNING_API_TOKEN
- name: MCP_TRANSPORT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: MCP_TRANSPORT
- name: AUTH_MODE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: AUTH_MODE
- name: LOG_LEVEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: LOG_LEVEL
# 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: SPANNING_PLATFORM, SPANNING_ADMIN_EMAIL, SPANNING_API_TOKEN, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsdocker run -i --rm -e SPANNING_PLATFORM -e SPANNING_ADMIN_EMAIL -e SPANNING_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/spanning-mcp:v1.1.3
{
"mcpServers": {
"spanning": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SPANNING_PLATFORM",
"-e",
"SPANNING_ADMIN_EMAIL",
"-e",
"SPANNING_API_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/spanning-mcp:v1.1.3"
],
"env": {
"SPANNING_PLATFORM": "${SPANNING_PLATFORM}",
"SPANNING_ADMIN_EMAIL": "${SPANNING_ADMIN_EMAIL}",
"SPANNING_API_TOKEN": "${SPANNING_API_TOKEN}",
"MCP_TRANSPORT": "${MCP_TRANSPORT}",
"AUTH_MODE": "${AUTH_MODE}",
"LOG_LEVEL": "${LOG_LEVEL}"
}
}
}
}
#!/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 spanning -e "SPANNING_PLATFORM=${SPANNING_PLATFORM}" -e "SPANNING_ADMIN_EMAIL=${SPANNING_ADMIN_EMAIL}" -e "SPANNING_API_TOKEN=${SPANNING_API_TOKEN}" -e "MCP_TRANSPORT=${MCP_TRANSPORT}" -e "AUTH_MODE=${AUTH_MODE}" -e "LOG_LEVEL=${LOG_LEVEL}" -- docker run -i --rm -e SPANNING_PLATFORM -e SPANNING_ADMIN_EMAIL -e SPANNING_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/spanning-mcp:v1.1.3
{
"mcpServers": {
"spanning": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SPANNING_PLATFORM",
"-e",
"SPANNING_ADMIN_EMAIL",
"-e",
"SPANNING_API_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/spanning-mcp:v1.1.3"
],
"env": {
"SPANNING_PLATFORM": "${SPANNING_PLATFORM}",
"SPANNING_ADMIN_EMAIL": "${SPANNING_ADMIN_EMAIL}",
"SPANNING_API_TOKEN": "${SPANNING_API_TOKEN}",
"MCP_TRANSPORT": "${MCP_TRANSPORT}",
"AUTH_MODE": "${AUTH_MODE}",
"LOG_LEVEL": "${LOG_LEVEL}"
}
}
}
}
{
"servers": {
"spanning": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SPANNING_PLATFORM",
"-e",
"SPANNING_ADMIN_EMAIL",
"-e",
"SPANNING_API_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/spanning-mcp:v1.1.3"
],
"env": {
"SPANNING_PLATFORM": "${SPANNING_PLATFORM}",
"SPANNING_ADMIN_EMAIL": "${SPANNING_ADMIN_EMAIL}",
"SPANNING_API_TOKEN": "${SPANNING_API_TOKEN}",
"MCP_TRANSPORT": "${MCP_TRANSPORT}",
"AUTH_MODE": "${AUTH_MODE}",
"LOG_LEVEL": "${LOG_LEVEL}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.wyre-technology/spanning-mcp
- not probed yet: tools unpinned, ingest lists them
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.