A command line for zingmp3.
zingmp3 is a single pure-Go binary. It reads public zingmp3 data
over plain HTTPS, shapes it into clean records, and prints output that pipes
into the rest of your tools. No API key, nothing to run alongside it.
The same package is also a resource-URI driver,
so a host program like ant can address
zingmp3 as zingmp3:// URIs.
go install github.com/tamnd/zingmp3-cli/cmd/zingmp3@latestOr grab a prebuilt binary from the releases, or run the container image:
docker run --rm ghcr.io/tamnd/zingmp3:latest --helpzingmp3 page <path> # fetch one page as a record
zingmp3 page <path> -o json # as JSON, ready for jq
zingmp3 page <path> --template '{{.Body}}' # just the readable body text
zingmp3 links <path> # the pages it links to, one per line
zingmp3 --help # the whole command treeEvery command shares one output contract: -o table|json|jsonl|csv|tsv|url|raw,
--fields to pick columns, --template for a custom line, and -n to limit.
The default adapts to where output goes (a table on a terminal, JSONL in a
pipe), so the same command reads well by hand and parses cleanly downstream.
This is a fresh scaffold. It ships one example resource type, page, wired end
to end. Model the real zingmp3 records in zingmp3/ and declare their
operations in zingmp3/domain.go; each one becomes a command, an HTTP
route, and an MCP tool at once.
The same operations are available over HTTP and as an MCP tool set for agents, with no extra code:
zingmp3 serve --addr :7777 # GET /v1/page/<path> returns NDJSON
zingmp3 mcp # speak MCP over stdiozingmp3 registers a zingmp3 domain the way a program registers a
database driver with database/sql. A host enables it with one blank import:
import _ "github.com/tamnd/zingmp3-cli/zingmp3"Then ant (or any program that links the package)
dereferences zingmp3:// URIs without knowing anything about zingmp3:
ant get zingmp3://page/<path> # fetch the record
ant cat zingmp3://page/<path> # just the body text
ant ls zingmp3://page/<path> # the pages it links to, each addressable
ant url zingmp3://page/<path> # the live https URLcmd/zingmp3/ thin main: hands cli.NewApp to kit.Run
cli/ assembles the kit App from the zingmp3 domain
zingmp3/ the library: HTTP client, data models, and domain.go (the driver)
docs/ tago documentation site
make build # ./bin/zingmp3
make test # go test ./...
make vet # go vet ./...Push a version tag and GitHub Actions runs GoReleaser, which builds the archives, Linux packages, the multi-arch GHCR image, checksums, SBOMs, and a cosign signature:
git tag v0.1.0
git push --tagsThe Homebrew and Scoop steps self-disable until their tokens exist, so the first release works with no extra secrets.
Apache-2.0. See LICENSE.