Self-hosted · Personal use

Xone Suno

v1.2.0 · © 2026

Your personal Suno Pro API — Suno V6 Flagship default, full endpoint coverage, MCP-ready.

What is Xone Suno?

Xone Suno is a self-hosted REST API wrapper that drives a personal Suno Pro account via session cookie — no third-party paid API, no rate-limited proxy. You run it on your own machine and call it with a bearer token.

  • Suno V6 by default — uses chirp-hawk (the latest Suno V6 flagship model) out of the box with alias support (v6, v6-wild, v6-mini, v5.5); override per-request or via SUNO_DEFAULT_MODEL env var.
  • Full endpoint coverage — generate, custom_generate, extend_audio, concat, generate_stems, generate_lyrics, get_aligned_lyrics, workspaces, download, history, webhooks, and more.
  • Async model — generation returns 2 clips instantly (status:"submitted"); poll GET /api/get?ids= until complete, or pass wait_audio:true to block.
  • MCP server included — drive Suno directly from Claude or any MCP-compatible agent (mcp/ directory, 48 tools).

Quick start

# 1. Copy your Suno session cookie from browser DevTools → SUNO_COOKIE in .env
# 2. Set an API_TOKEN in .env (any random secret)
npm run dev          # starts on http://localhost:3939

For full setup details (cookie extraction, 2Captcha, environment variables) see RUN.md.


UIs

| URL | Description | |---|---| | /studio | Playground — create songs, poll status, play audio, save files | | /docs | Swagger API explorer — full OpenAPI 3.0.3, try every endpoint |


Usage guide & recipes

See docs/GUIDE.md for end-to-end recipes:

  • Bilingual "Sing to Learn English" episode (Vietnamese + English duet, industrial/electro)
  • Instrumental loop for video backgrounds
  • Stems for remix/karaoke
  • Batch by workspace
  • Webhook into a pipeline

MCP (Claude integration)

claude mcp add xone-suno -e SUNO_API_TOKEN=<API_TOKEN> -e SUNO_API_BASE=http://localhost:3939 -- node <abs-path>/mcp/dist/index.js

Then ask Claude: "make a synthwave song called Night Ride and wait for it."


Personal use only — you accept Suno ToS/account risk when using the cookie approach.