docs
Environments
Where Cadenza runs and how to point clients at it.
Last updated 2026-07-10 · beta
Production
| Surface | URL |
|---|---|
| Web app and REST API | https://cadenza.media |
| API base | https://cadenza.media/api/v1 |
| Remote MCP endpoint | https://cadenza.media/api/mcp |
Note: The remote MCP endpoint is live (OAuth 2.1). https://mcp.cadenza.media/mcp is the same server under a shorter name once its DNS record is published; local stdio connections via npx cadenza connect work independently of it.
Local development
The MCP server and CLI honor CADENZA_API_URL to point at a non-production API, and the API honors CADENZA_DATA_DIR for an isolated data directory. No secret ever lives in a config file; keys come from the connect flow or the CADENZA_API_KEY environment variable.
Versioning
The REST surface is versioned in the path (/api/v1). Breaking changes ship as a new version; v1 request shapes stay stable during the beta and changes are recorded in the changelog.