Arxpot MCP

Remote MCP server for the Arxpot processing core. It gives an MCP client music search, full track/collection metadata, download jobs, job progress, history, remote storage delivery, and downloadable audio files.

arxpot-mcp is intentionally a separate service. It does not reproduce FFmpeg, matching, or downloader logic: the private Go Arxpot backend remains the single processing core.

Tools

Related MCP server: beatport-mcp-server

Local try-out

Clone this repository next to arxpot, then run:

cp .env.example .env
docker compose -f docker-compose.local.yml up --build

The MCP endpoint is http://127.0.0.1:3000/mcp. Arxpot is not published to the host in this stack.

For local MCP clients, set MCP_AUTH_TOKEN and send Authorization: Bearer <token>. For a temporary no-auth test only, leave it blank and use a long secret MCP_PATH, such as /mcp/<random-value>.

ChatGPT and Tailscale Funnel

Run arxpot and arxpot-mcp in the same Tailscale network namespace. Funnel must proxy only the MCP container on port 3000; the Go core remains private.

tailscale funnel --bg --https=443 http://127.0.0.1:3000

Set PUBLIC_BASE_URL=https://<tailscale-host>.<tailnet>.ts.net. The download_file tool then returns a temporary URL under /files/…; the MCP service proxies the private signed Arxpot link and never reveals the core address.

For a durable ChatGPT connection, use OAuth in front of /mcp. The optional MCP_AUTH_TOKEN is for local clients and API testing, not the final ChatGPT authentication flow.

Development

npm install
npm run build
npm test