Installation

The CLI ships as a Docker image at spanly/spanly:latest (Docker Hub) and ghcr.io/spanly/spanly:latest (GHCR). It is the same Go binary that npm and Homebrew install, so all subcommands and flags work identically.

Pull

docker pull spanly/spanly:latest

Run

# Wrap a containerised MCP server (same network / compose sidecar):docker run --rm \  -e SPANLY_API_KEY="$SPANLY_API_KEY" \  spanly/spanly:latest run -- node /app/server.js# Or proxy an MCP server reachable from the container.# Point your MCP client at localhost:3001.docker run --rm \  -e SPANLY_API_KEY="$SPANLY_API_KEY" \  -p 3001:3001 \  spanly/spanly:latest proxy host.docker.internal:3000 0.0.0.0:3001

For most users the proxy form is the more useful shape inside a container, since the wrapped child (run -- …) would itself need to be inside the same image. If your MCP server is already a container, run Spanly alongside it and proxy. See Sidecar patterns for compose and Kubernetes examples.

Image tags

Image contents

• A single static Go binary at /usr/local/bin/spanly.
• The default ENTRYPOINT is spanly so you only pass subcommand + flags as command: / args:.
• Built for linux/amd64 and linux/arm64.

Local development

To run against your local dev Spanly stack, override the ingest URL:

docker run --rm \
  -e SPANLY_API_KEY=spanly_us_localdev \
  -e SPANLY_INGEST_URL=http://host.docker.internal:3010 \
  spanly/spanly:latest proxy host.docker.internal:3000 0.0.0.0:3001