MCPOverview

MCP Protocol

Patrons Only

ONCE MCP provides a Model Context Protocol endpoint for agent-driven release submission. Collect metadata, upload assets, and submit releases through a single programmatic interface.

Current Scope

  • Releases are distributed to all stores (store selection coming soon)
  • Accepts a subset of metadata fields compared to the ONCE app
  • No validation agent or mastering in the MCP flow

Workflow

The typical MCP flow has three steps:

  1. Authenticate — Use auth_login or POST /api/mcp/auth/login to get an access token
  2. Upload assets — Upload cover art and audio via upload_file, upload_file_from_url, or HTTP endpoints
  3. Submit release — Call submit_release with metadata, then poll status endpoints

Discovery

ResourceEndpoint
MCP endpointPOST /api/mcp
Server cardGET /.well-known/mcp/server-card.json

MCP Resources

ONCE MCP exposes two read-only resources via resources/list and resources/read:

  • mcp://docs/agent-guide — Protocol guide (markdown)
  • mcp://schemas/release-required — Required fields and example payload (JSON)
HomeQuickstart