mcp

Mcp Publish Cdn

Trigger a CDN release from MCP — same orchestration as the user-JWT POST /v1/projects/{id}/cdn/releases, but addressable via the MCP tool publish_cdn. Plan-cap soft warns are surfaced via soft_warn=true; hard caps still raise 403.

post/v1/mcp/projects/{project_id}/cdn/releases

Request

  • Base URL: https://api.sonenta.dev
  • URL: https://api.sonenta.dev/v1/mcp/projects/{project_id}/cdn/releases
  • Auth: none declared

Path parameters

project_idstring required

Request body

language_codestring nullable
namespacestring nullable
version_slugstring nullable

Project-version slug. Defaults to the production version.

forceboolean

Currently a no-op: orchestrate_publish is already idempotent + content-addressed, so re-running with no changes returns reused releases. Reserved for V2 when we want to bypass dedup.

allow_emptyboolean

By default a base bundle whose namespace has keys but ZERO publishable ones (all below 'translated', e.g. draft) is REFUSED (publishing it would serve an EMPTY bundle) and reported in warnings. Set true to force-publish the empty bundle anyway.

Response

Successful Response

new_countinteger required
reused_countinteger required
soft_warnboolean

Changes

No recorded changes to this operation across all 1 revision of this API.